From: Tom de Vries <tdevries@suse.de>
To: Andreas Schwab <schwab@linux-m68k.org>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/testsuite] Fix 64-bit dwarf test-cases with -m32
Date: Wed, 3 Nov 2021 21:00:53 +0100 [thread overview]
Message-ID: <32e918ff-583b-cc04-4f67-09b160b6d3cb@suse.de> (raw)
In-Reply-To: <874k8vfvg4.fsf@igel.home>
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 ?
Thanks,
- Tom
next prev parent reply other threads:[~2021-11-03 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 17:56 Tom de Vries
2021-11-01 20:54 ` Andreas Schwab
2021-11-03 20:00 ` Tom de Vries [this message]
2021-11-03 20:30 ` Andreas Schwab
2021-11-19 14:08 ` Tom de Vries
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32e918ff-583b-cc04-4f67-09b160b6d3cb@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).