From: Luis Machado <luis.machado@arm.com>
To: Tom Tromey <tom@tromey.com>,
Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Cc: Pedro Alves <pedro@palves.net>
Subject: Re: [PATCH] Move 64-bit BFD files from ALL_TARGET_OBS to ALL_64_TARGET_OBS
Date: Thu, 26 May 2022 18:50:57 +0100 [thread overview]
Message-ID: <4d719369-2443-758a-40d4-3290bc35d9df@arm.com> (raw)
In-Reply-To: <878rqo8kev.fsf@tromey.com>
On 5/26/22 14:59, Tom Tromey wrote:
>>>>>> "Luis" == Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Luis> 32-bit builds with --enable-targets=all are still failing due to
> Luis> the misplacement of these places.
>
> Luis> If we drop the tilegx change, would that be acceptable?
>
> IIUC, the original objection was that tilegx was listed as 32-bit in
> opcodes, but was moved to the 64-bit section in your patch. However,
> tilegx is actually a 64-bit arch, so you sent another patch to correct
> this in opcodes.>
> If that's all true then I think your patch is correct as-is and should
> be checked in.
Thanks Tom.
Indeed. There has been some discussions on binutils@. Sounds like we need to fix a few
more things, but this patch should address the GDB side of things for now.
>
> Thank you for doing this.
>
> Tom
next prev parent reply other threads:[~2022-05-26 17:51 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 [this message]
2022-05-03 15:21 ` Tom Tromey
2022-05-03 16:20 ` Luis Machado
2022-05-04 8:00 ` Luis Machado
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=4d719369-2443-758a-40d4-3290bc35d9df@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--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).