From: Alan Modra <amodra@gmail.com>
To: "Steinar H. Gunderson" <sesse@google.com>
Cc: Jan Beulich <jbeulich@suse.com>,
sesse@chromium.org, binutils@sourceware.org,
Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] Add a trie to map quickly from address range to compilation unit.
Date: Sun, 3 Apr 2022 21:09:58 +0930 [thread overview]
Message-ID: <YkmHjl0ptQH/Jbdw@squeak.grove.modra.org> (raw)
In-Reply-To: <YkVIfPKM+p0MWUlQ@google.com>
On Thu, Mar 31, 2022 at 08:21:48AM +0200, Steinar H. Gunderson wrote:
> On Tue, Mar 29, 2022 at 08:07:07AM +0200, Jan Beulich wrote:
> > Yeah, makes sense to me. I guess if bad input was to be worked around
> > again, a testcase covering the specific situation would want adding, so
> > it won't be lost what specifically is to be worked around.
>
> I'm fine with just removing the range handling logic if that's what you
> decide. :-) Let me know when/if a patch goes in, and I'll send a v3 that
> is adjusted.
Let's do that. I'll commit the patch I've already posted.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-04-03 11:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 9:40 Steinar H. Gunderson
2022-03-23 14:14 ` Nick Clifton
2022-03-23 15:53 ` Steinar H. Gunderson
2022-03-23 22:24 ` Steinar H. Gunderson
2022-03-24 5:22 ` Alan Modra
2022-03-24 8:01 ` Steinar H. Gunderson
2022-03-24 23:30 ` Alan Modra
2022-03-25 0:01 ` Steinar H. Gunderson
2022-03-28 10:19 ` Jan Beulich
2022-03-28 23:47 ` Alan Modra
2022-03-29 6:07 ` Jan Beulich
2022-03-31 6:21 ` Steinar H. Gunderson
2022-04-03 11:39 ` Alan Modra [this message]
2022-04-04 7:29 ` Steinar H. Gunderson
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=YkmHjl0ptQH/Jbdw@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=nickc@redhat.com \
--cc=sesse@chromium.org \
--cc=sesse@google.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).