From: Pedro Alves <pedro@palves.net>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: jbeulich@suse.com, binutils@sourceware.org, amodra@gmail.com
Subject: Re: 32-bit archs, want64=true, and gas integers
Date: Fri, 6 May 2022 15:44:47 +0100 [thread overview]
Message-ID: <9a76c303-f502-41d6-473e-644cfa94d547@palves.net> (raw)
In-Reply-To: <20220506143245.D5C8C2044E@pchp3.se.axis.com>
On 2022-05-06 15:32, Hans-Peter Nilsson wrote:
>> From: Pedro Alves <pedro@palves.net>
>> Date: Fri, 6 May 2022 12:43:27 +0200
>
>> If something like this went in, then I assume that cris could go back to not setting
>> want64=yes.
>> [gas expr patch]
>
> While something like that could work (thanks for your work),
> I still prefer having all binutils behavior consistent
> regardless of host 32/64-bitness.
Can't argue with that. As I mentioned, GDB switched to always using 64-bit CORE_ADDR
a few years ago. I've never heard anyone complain about that causing slowdown or higher
memory usage. Plus, who develops on 32-bit hosts nowadays, anyhow?
> There's at least objdump output too.
Curious, what sort of objdump output difference does 32-bit/64-bit bfd cause?
next prev parent reply other threads:[~2022-05-06 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 7:56 [PATCH] Don't define ARCH_cris for BFD64 Luis Machado
2022-05-04 8:08 ` Alan Modra
2022-05-04 8:15 ` Luis Machado
2022-05-04 8:39 ` Alan Modra
2022-05-04 14:37 ` Hans-Peter Nilsson
2022-05-04 22:37 ` Alan Modra
2022-05-05 9:01 ` Luis Machado
2022-05-05 11:11 ` Pedro Alves
2022-05-05 12:56 ` Hans-Peter Nilsson
2022-05-06 0:56 ` Alan Modra
2022-05-06 2:35 ` Hans-Peter Nilsson
2022-05-06 9:09 ` Luis Machado
2022-05-06 9:00 ` 32-bit archs, want64=true, and gas integers (Re: [PATCH] Don't define ARCH_cris for BFD64) Pedro Alves
2022-05-06 9:55 ` 32-bit archs, want64=true, and gas integers Jan Beulich
2022-05-06 10:01 ` Pedro Alves
2022-05-06 10:17 ` Jan Beulich
2022-05-06 10:43 ` Pedro Alves
2022-05-06 11:55 ` Jan Beulich
2022-05-06 12:04 ` Pedro Alves
2022-05-06 14:32 ` Hans-Peter Nilsson
2022-05-06 14:44 ` Pedro Alves [this message]
2022-05-07 20:19 ` Hans-Peter Nilsson
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=9a76c303-f502-41d6-473e-644cfa94d547@palves.net \
--to=pedro@palves.net \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hp@axis.com \
--cc=jbeulich@suse.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).