[PATCH] [gdb/testsuite] Fix 64-bit dwarf test-cases with -m32
Andreas Schwab
schwab@linux-m68k.org
Wed Nov 3 20:30:12 GMT 2021
On Nov 03 2021, Tom de Vries wrote:
> On 11/1/21 9:54 PM, Andreas Schwab wrote:
>> On Nov 01 2021, Tom de Vries via Gdb-patches wrote:
>>
>>> When running test-case gdb.dwarf2/loc-sec-offset.exp with target board -m32,
>>> I run into:
>>> ...
>>> builtin_spawn -ignore SIGHUP gcc -fno-stack-protector -m32 \
>>> -fdiagnostics-color=never -c -o loc-sec-offset-dw641.o \
>>> loc-sec-offset-dw64.S^M
>>> as: loc-sec-offset-dw641.o: unsupported relocation type: 0x1^M
>>> loc-sec-offset-dw64.S: Assembler messages:^M
>>> loc-sec-offset-dw64.S:29: Error: cannot represent relocation type \
>>> BFD_RELOC_64^M
>>> ...
>>>
>>> Looking at line 29, we have:
>>> ...
>>> .8byte .Labbrev1_begin /* Abbrevs */
>>> ...
>>>
>>> It would be nice if the assembler could handle this somehow. But I guess
>>> it's not unreasonable that an assembler for a 32-bit architecture will object
>>> to handling 64-bit labels.
>>
>> Shouldn't the 64-bit dwarf tests just be skipped on 32-bit targets?
>
> Because ?
Because 32-bit targets have no way to represent 8-byte relocations.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
More information about the Gdb-patches
mailing list