From: Michael Matz <matz@suse.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: ld: Avoid overflows in string merging
Date: Wed, 8 Nov 2023 16:16:30 +0000 (UTC) [thread overview]
Message-ID: <alpine.LSU.2.20.2311081613460.15233@wotan.suse.de> (raw)
In-Reply-To: <alpine.LSU.2.20.2311081339580.15233@wotan.suse.de>
Hey,
On Wed, 8 Nov 2023, Michael Matz wrote:
> > Otoh aren't we also at risk of underestimating when entsize == 1 and
> > we're not dealing with strings?
>
> Hmm, that's true. I need to fix that.
Ah, no. I remember: the nr of buckets starts out as 0x2000, which is
impossible to reach by distinct size 1 entities, no matter how
underestimating the estimation is. So, it's confusing but not wrong :)
Ciao,
Michael.
next prev parent reply other threads:[~2023-11-08 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 16:51 Michael Matz
2023-11-08 7:30 ` Jan Beulich
2023-11-08 14:31 ` Michael Matz
2023-11-08 16:16 ` Michael Matz [this message]
2023-11-09 7:55 ` Jan Beulich
2023-11-09 7:52 ` Jan Beulich
2023-11-09 16:27 ` Michael Matz
2023-11-10 10:10 ` Jan Beulich
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=alpine.LSU.2.20.2311081613460.15233@wotan.suse.de \
--to=matz@suse.de \
--cc=binutils@sourceware.org \
--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).