From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/testsuite] Fix 64-bit dwarf test-cases with -m32
Date: Mon, 01 Nov 2021 21:54:35 +0100 [thread overview]
Message-ID: <874k8vfvg4.fsf@igel.home> (raw)
In-Reply-To: <20211101175611.32103-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Mon, 1 Nov 2021 18:56:11 +0100")
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?
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."
next prev parent reply other threads:[~2021-11-03 18: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 [this message]
2021-11-03 20:00 ` Tom de Vries
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=874k8vfvg4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.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).