From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@arm.com>, Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH, v2] Fix 32-bit build for --enable-targets=all
Date: Wed, 27 Apr 2022 10:57:26 +0100 [thread overview]
Message-ID: <4726c20b-261b-ca39-a88d-f5e72892186b@palves.net> (raw)
In-Reply-To: <e6bc4fec-ffe7-44ee-adb8-71d48d133006@arm.com>
On 2022-04-26 07:31, Luis Machado via Binutils wrote:
>>
>
> Maybe some targets shouldn't be accepted as part of a 32-bit --enable-targets=all for GDB/sim. Removing those "problematic" targets from the list might be another possible approach I suppose.
That is already the case. See ALL_64_TARGET_OBS vs ALL_TARGET_OBS in gdb/Makefile.in:
# All target-dependent objects files that require 64-bit CORE_ADDR
# (used with --enable-targets=all --enable-64-bit-bfd).
ALL_64_TARGET_OBS = \
# All other target-dependent objects files (used with --enable-targets=all).
ALL_TARGET_OBS = \
Sounds like you'd just want to move bpf-tdep.o from ALL_TARGET_OBS to ALL_64_TARGET_OBS.
next prev parent reply other threads:[~2022-04-27 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:25 Luis Machado
2022-04-24 14:58 ` Joel Brobecker
2022-04-25 7:40 ` Luis Machado
2022-04-26 2:52 ` Alan Modra
2022-04-26 6:31 ` Luis Machado
2022-04-26 11:43 ` Alan Modra
2022-04-27 9:57 ` Pedro Alves [this message]
2022-04-27 11:25 ` Luis Machado
2022-04-26 8:07 ` Jose E. Marchesi
2022-04-26 13:22 ` Alan Modra
2022-04-29 12:35 ` Luis Machado
2022-04-29 16:22 ` Pedro Alves
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=4726c20b-261b-ca39-a88d-f5e72892186b@palves.net \
--to=pedro@palves.net \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=luis.machado@arm.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).