From: Alan Modra <amodra@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Subject: Re: PING^2: [PATCH v3] elf: Always honor the first definition in shared object and archive
Date: Sat, 6 Apr 2024 08:46:55 +1030 [thread overview]
Message-ID: <ZhB4VxswCBRD0I+O@squeak.grove.modra.org> (raw)
In-Reply-To: <CAMe9rOqFbq69LRRxS2f_7DFSA5uEtOR+8sQSV0rmcBcEz9GE6w@mail.gmail.com>
On Fri, Apr 05, 2024 at 05:00:28AM -0700, H.J. Lu wrote:
> On Fri, Apr 5, 2024 at 3:15 AM Nick Clifton <nickc@redhat.com> wrote:
> >
> > Hi H.J.
> >
> > >>> GCC doesn't put builtin function symbol references, which are defined in
> > >>> the shared C library, in the IR symbol table. When linker rescans shared
> > >>> objects and archives for newly added symbol references generated from the
> > >>> IR inputs, it skips definitions of the builtin functions in shared
> > >>> objects and archives.
> > >>>
> > >>> Add first_hash to elf_link_hash_table to track unreferenced definitions
> > >>> defined first in shared objects and archives. Always use them to resolve
> > >>> any references.
> >
> > Approved - please apply.
> >
> > Cheers
> > Nick
> >
>
> I am checking in the v2 patch:
>
> https://sourceware.org/pipermail/binutils/2024-April/133395.html
I had some further requests to make.
1) If you are going to use a bfd_hash_table based first_hash, please
don't use bfd_link_hash_table. Instead extend bfd_hash_entry with a
single abfd field. You'll need to write a newfunc, but that's about
all that is required. There are multiple examples of this in the
source, eg. bfd/stabs.c stab_link_includes_entry.
2) You are accessing freed memory in _bfd_elf_link_hash_table_free.
Free first_hash before freeing the main hash table. That needs fixing
immediately.
3) Please ensure tests have different names. This
[list {pr31482a} \
{-Wl,--no-as-needed,-R,tmpdir} {} \
{pr31482a.c} {pr31482a.exe} {pass.out} {-flto} {c} {} \
{tmpdir/pr31482b.a tmpdir/pr31482c.so}] \
[list {pr31482b} \
{-Wl,--no-as-needed,-R,tmpdir} {} \
{pr31482a.c} {pr31482b.exe} {pass1.out} {-flto} {c} {} \
{tmpdir/pr31482c.so tmpdir/pr31482b.a}] \
[list {pr31489a} \
{-Wl,--as-needed,-R,tmpdir} {} \
{pr31482a.c} {pr31489a.exe} {pass.out} {-flto} {c} {} \
{tmpdir/pr31482b.a tmpdir/pr31482c.so}] \
[list {pr31489b} \
{-Wl,--as-needed,-R,tmpdir} {} \
{pr31482a.c} {pr31489b.exe} {pass1.out} {-flto} {c} {} \
{tmpdir/pr31482c.so tmpdir/pr31482b.a}] \
has two tests called pr31489a and two called pr31489b.
"FAIL: pr31489a" as the output of make check isn't as helpful as it
could be. Better would be to add --no-as-needed and --as-needed to
the test names.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2024-04-05 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 19:43 H.J. Lu
2024-03-28 13:30 ` PING: " H.J. Lu
2024-04-04 13:29 ` PING^2: " H.J. Lu
2024-04-05 10:15 ` Nick Clifton
2024-04-05 12:00 ` H.J. Lu
2024-04-05 22:16 ` Alan Modra [this message]
2024-04-05 23:37 ` H.J. Lu
2024-04-05 23:45 ` Alan Modra
2024-04-05 23:48 ` H.J. Lu
2024-04-04 23:54 ` Alan Modra
2024-04-05 1:50 ` 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=ZhB4VxswCBRD0I+O@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=nickc@redhat.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).