From: Jan Beulich <jbeulich@suse.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: binutils@sourceware.org
Subject: Re: Fix read_ranges for 32-bit long
Date: Fri, 17 Nov 2023 10:12:27 +0100 [thread overview]
Message-ID: <176041da-2d6a-4bf2-a3b6-a4154b9c4773@suse.com> (raw)
In-Reply-To: <82567b93-7ea5-bdbf-2940-59ad7c658f61@codesourcery.com>
On 17.11.2023 00:35, Joseph Myers wrote:
> bfd/dwarf2.c:read_ranges compares bfd_vma values against -1UL, which
> doesn't work correctly when long is 32-bit and bfd_vma is 64-bit
> (observed as "nm -l" being very slow for mingw64 host; probably causes
> issues on 32-bit hosts as well as IL32LLP64 cases such as mingw64).
> Fix by using (bfd_vma) -1 in place of -1UL, as done elsewhere.
>
> ---
>
> OK to commit?
Yes. And thanks.
Jan
prev parent reply other threads:[~2023-11-17 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 23:35 Joseph Myers
2023-11-17 9:12 ` Jan Beulich [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=176041da-2d6a-4bf2-a3b6-a4154b9c4773@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.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).