From: Carlos O'Donell <carlos@redhat.com>
To: Fangrui Song <i@maskray.me>, libc-help@sourceware.org
Subject: Re: Lightning talk notes on glibc
Date: Wed, 20 Jan 2021 11:20:52 -0500 [thread overview]
Message-ID: <c0f4cabc-f97d-ab36-2bab-15282f7711ff@redhat.com> (raw)
In-Reply-To: <20210120074815.k6km6cmhrt4aknpo@gmail.com>
On 1/20/21 2:48 AM, Fangrui Song wrote:
> The `-O2` issue is probably related to (1) expected inlining and (2) avoiding dynamic relocations.
Not "probably related to" but absolutely about (2).
And (1) is directly related to (2). If a function is not inlined you will
generate relocations that cannot be handled during the bootstrap.
The core bootstrap must be free of relocations in this sense.
As Adhemerval points out there is value in minimizing the bootstrap set
to allow for more complex debugging tools be used *after* the bootstrap.
Like being able to run with sanitizers turned on.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-01-20 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:48 Fangrui Song
2021-01-20 16:17 ` Adhemerval Zanella
2021-01-20 16:20 ` Carlos O'Donell [this message]
2021-01-20 16:25 ` Carlos O'Donell
2021-01-20 16:25 ` Carlos O'Donell
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=c0f4cabc-f97d-ab36-2bab-15282f7711ff@redhat.com \
--to=carlos@redhat.com \
--cc=i@maskray.me \
--cc=libc-help@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).