From: Tom Tromey <tom@tromey.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: chew.c printf of intptr_t
Date: Tue, 28 Feb 2023 13:24:28 -0700 [thread overview]
Message-ID: <87356ptu6b.fsf@tromey.com> (raw)
In-Reply-To: <Y/1M54x/w6QMpPfQ@squeak.grove.modra.org> (Alan Modra's message of "Tue, 28 Feb 2023 11:07:59 +1030")
>>>>> "Alan" == Alan Modra <amodra@gmail.com> writes:
Alan> Seen when building binutils with gcc -m32 on x86_64-linux.
[...]
Thank you for the fix.
Tom
prev parent reply other threads:[~2023-02-28 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 0:37 Alan Modra
2023-02-28 20:24 ` Tom Tromey [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=87356ptu6b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/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).