From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>,
hjl.tools@gmail.com, ndesaulniers@google.com, mbenes@suse.cz,
rostedt@goodmis.org, linux-toolchains@vger.kernel.org
Subject: Re: The trouble with __weak and objtool got worse
Date: Sat, 16 Apr 2022 12:59:14 -0500 [thread overview]
Message-ID: <20220416175914.GF25951@gate.crashing.org> (raw)
In-Reply-To: <20220416132005.GE25951@gate.crashing.org>
On Sat, Apr 16, 2022 at 08:20:06AM -0500, Segher Boessenkool wrote:
> On Sat, Apr 16, 2022 at 12:59:05PM +0200, Peter Zijlstra wrote:
> > On Fri, Apr 15, 2022 at 01:22:29PM -0500, Segher Boessenkool wrote:
> > > On Fri, Apr 15, 2022 at 01:19:04PM +0200, Peter Zijlstra wrote:
> > > > The other option seems to be to have objtool add section symbols it
> > > > needs, however due to ELF being a total PITA and requiring all LOCAL
> > > > symbols to be before GLOBAL symbols, this would mean re-ordering the
> > > > whole symbol table (I have the code somewhere :-/).
> > >
> > > ELF requires no such thing? Where do you see this?
> >
> > The first google hit:
> >
> > https://docs.oracle.com/cd/E23824_01/html/819-0690/chapter6-79797.html
> >
> > which has:
> >
> > "In each symbol table, all symbols with STB_LOCAL binding precede the
> > weak symbols and global symbols. As Sections describes, a symbol table
> > section's sh_info section header member holds the symbol table index for
> > the first non-local symbol."
>
> That is not the ELF spec, and it is incorrect afaics. Do you have any
> authorative reference?
It is on page 1-18 of the ELF specification version 1.1, at the bottom
of the page. How unfortunate. It says:
In each symbol table, all symbols with STB_LOCAL binding preced the
weak and global symbols. As ``Sections'' above describes, a symbol
table section's sh_info section header member holds the symbol table
index for the first non-local symbol.
so it is an optimisation, assuming that there are significantly fewer
local than global symbols.
Segher
next prev parent reply other threads:[~2022-04-16 18:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 11:19 The trouble with __weak and objtool got worse Peter Zijlstra
2022-04-15 14:12 ` Steven Rostedt
2022-04-15 15:31 ` Peter Zijlstra
2022-04-15 15:10 ` Josh Poimboeuf
2022-04-15 15:15 ` Josh Poimboeuf
2022-04-15 15:26 ` Peter Zijlstra
2022-04-15 17:40 ` Nick Desaulniers
2022-04-15 18:21 ` Josh Poimboeuf
2022-04-15 18:23 ` Josh Poimboeuf
2022-04-15 20:36 ` Nick Desaulniers
2022-04-16 10:49 ` Peter Zijlstra
2022-04-16 10:48 ` Peter Zijlstra
2022-04-16 16:07 ` Josh Poimboeuf
2022-04-16 16:32 ` H.J. Lu
2022-04-17 15:44 ` Peter Zijlstra
2022-04-17 15:46 ` Peter Zijlstra
2022-04-15 18:22 ` Segher Boessenkool
2022-04-15 18:36 ` Nick Desaulniers
2022-04-15 20:07 ` Segher Boessenkool
2022-04-15 20:31 ` Nick Desaulniers
2022-04-15 21:17 ` Fangrui Song
2022-04-15 21:41 ` Segher Boessenkool
2022-04-16 11:09 ` Peter Zijlstra
2022-04-16 10:59 ` Peter Zijlstra
2022-04-16 13:20 ` Segher Boessenkool
2022-04-16 17:59 ` Segher Boessenkool [this message]
2022-04-15 21:04 ` H.J. Lu
2022-04-16 11:25 ` Peter Zijlstra
2022-04-16 16:27 ` H.J. Lu
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=20220416175914.GF25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=hjl.tools@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-toolchains@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.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 NNTP newsgroup(s).