From: Luis Machado <luis.machado@arm.com>
To: Tom Tromey <tom@tromey.com>,
Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Move 64-bit BFD files from ALL_TARGET_OBS to ALL_64_TARGET_OBS
Date: Wed, 4 May 2022 09:00:02 +0100 [thread overview]
Message-ID: <c66de069-e66d-ccdb-0f55-6de8d0293c1a@arm.com> (raw)
In-Reply-To: <7c844200-a6be-97f8-7595-6c64b266fb9c@arm.com>
On 5/3/22 17:20, Luis Machado via Gdb-patches wrote:
> Hi Tom,
>
> On 5/3/22 16:21, Tom Tromey wrote:
>>>>>>> "Luis" == Luis Machado via Gdb-patches
>>>>>>> <gdb-patches@sourceware.org> writes:
>>
>> Luis> Doing a 32-bit build with "--enable-targets=all --disable-sim"
>> fails to link
>> Luis> properly.
>>
>> FWIW this patch seems like a candidate for the gdb 12 branch to me.
>> Is there a bug open for this problem in bugzilla?
>
> No. We've discussed this somewhat on gdb-patches@ and binutils@, but the
> conclusion was that it didn't look like a blocker for the release. I can
> open a ticket and prepare a backport to GDB 12.
Here it is: https://sourceware.org/bugzilla/show_bug.cgi?id=29119
prev parent reply other threads:[~2022-05-04 8:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:19 Luis Machado
2022-05-03 11:24 ` Pedro Alves
2022-05-03 11:30 ` Luis Machado
2022-05-03 21:51 ` Luis Machado
2022-05-05 9:06 ` Luis Machado
2022-05-05 10:29 ` Pedro Alves
2022-05-30 10:25 ` Luis Machado
2022-05-26 7:22 ` Luis Machado
2022-05-26 13:57 ` Simon Marchi
2022-05-26 17:45 ` Luis Machado
2022-05-26 13:59 ` Tom Tromey
2022-05-26 17:50 ` Luis Machado
2022-05-03 15:21 ` Tom Tromey
2022-05-03 16:20 ` Luis Machado
2022-05-04 8:00 ` Luis Machado [this message]
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=c66de069-e66d-ccdb-0f55-6de8d0293c1a@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).