From: Pedro Alves <pedro@palves.net>
To: Jan Beulich <jbeulich@suse.com>
Cc: Hans-Peter Nilsson <hp@axis.com>,
binutils@sourceware.org, Alan Modra <amodra@gmail.com>
Subject: Re: 32-bit archs, want64=true, and gas integers
Date: Fri, 6 May 2022 13:04:35 +0100 [thread overview]
Message-ID: <d354c4b1-f584-4173-8cfe-8ea249950305@palves.net> (raw)
In-Reply-To: <df9f9f0a-9588-3a31-1a06-ab4e29c6d7f1@suse.com>
On 2022-05-06 12:55, Jan Beulich wrote:
>> diff --git a/gas/as.h b/gas/as.h
>> index 135abc8f23d..5b636cfd59a 100644
>> --- a/gas/as.h
>> +++ b/gas/as.h
>> @@ -139,7 +139,7 @@ typedef bfd_vma addressT;
>> typedef bfd_signed_vma offsetT;
>>
>> /* Type of symbol value, etc. For use in prototypes. */
>> -typedef addressT valueT;
>> +typedef uint64_t valueT;
>
> ... I'd be afraid this might alter behavior for purely 32-bit targets.
> Whether such a behavioral change would be deemed okay I'm not sure.
My thinking is that if that were a problem in practice, --enable-64-bit-bfd would already
have such a problem, but I couldn't find anything in gas's configure rejecting that option
for any target. I looked a bit around in bugzilla and didn't find anyone complaining about gas
32-bit vs 64-bit behavior on 32-bit archs, and didn't find anything, but admittedly
I may have not searched properly.
next prev parent reply other threads:[~2022-05-06 12:04 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 [this message]
2022-05-06 14:32 ` Hans-Peter Nilsson
2022-05-06 14:44 ` Pedro Alves
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=d354c4b1-f584-4173-8cfe-8ea249950305@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).