public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] elf: Don't load archive element after dynamic definition
Date: Fri, 28 Aug 2020 11:28:48 +0930	[thread overview]
Message-ID: <20200828015847.GG15695@bubble.grove.modra.org> (raw)
In-Reply-To: <CAMe9rOrYkPNPjoaESP-5B=nDggB_DSd=X7NTD3mu_QtDRTd0Vw@mail.gmail.com>

On Thu, Aug 27, 2020 at 07:05:15AM -0700, H.J. Lu wrote:
> On Thu, Aug 27, 2020 at 6:53 AM Alan Modra <amodra@gmail.com> wrote:
> >
> > On Tue, Aug 25, 2020 at 10:28:42AM -0700, H.J. Lu via Binutils wrote:
> > > Don't load the archive element after seeing a definition in a shared
> > > object.
> > >
> > > bfd/
> > >
> > >       PR ld/26530
> > >       * elflink.c (elf_link_add_object_symbols): Also preserve the
> > >       dynamic_def bit for --as-needed.
> > >       (elf_link_add_archive_symbols): Don't load the archive element
> > >       after seeing a definition in a shared object.
> >
> > This seems over complicated to me.  Why don't we just load the
> > as-needed shared library on the first pass?
> >
> 
> In the first pass, when we are loading a shared object,  do we have
> the IR symbol resolution?

No, but why should that matter?  Adding DT_NEEDED for an as-needed
library that turns out to not be needed after LTO is not a problem
IMO.  Also I think it may be necessary to load shared libraries on the
first pass for LTO to work properly in corner cases.  See the comment
in git commit a896df97b952.

The condition we use to add --as-needed libraries is:
	  if (!add_needed
	      && matched
	      && definition
	      && ((dynsym
		   && h->ref_regular_nonweak)
		  || (h->ref_dynamic_nonweak
		      && (elf_dyn_lib_class (abfd) & DYN_AS_NEEDED) != 0
		      && !on_needed_list (elf_dt_name (abfd),
					  htab->needed, NULL))))
Note the test of dynsym, but earlier
	  /* Nor should we make plugin symbols dynamic.  */
	  if ((abfd->flags & BFD_PLUGIN) != 0)
	    dynsym = FALSE;

So I'm thinking perhaps we should delete the above lines and instead
add the BFD_PLUGIN condition where we make symbols dynamic.

	  if (dynsym && (abfd->flags & BFD_PLUGIN) == 0 && h->dynindx == -1)
	    {
	      if (! bfd_elf_link_record_dynamic_symbol (info, h))

I haven't tested the idea..

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2020-08-28  1:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 17:28 H.J. Lu
2020-08-27 13:53 ` Alan Modra
2020-08-27 14:05   ` H.J. Lu
2020-08-28  1:58     ` Alan Modra [this message]
2020-08-28 12:53       ` H.J. Lu
2020-08-28 14:49         ` Alan Modra
2020-08-28 14:50           ` H.J. Lu
2020-09-02  6:52             ` Martin Liška
2020-09-02  8:12               ` Alan Modra
2020-09-02 11:56                 ` H.J. Lu
2020-09-02 13:05                   ` Alan Modra
2020-09-02 13:22                     ` H.J. Lu
2020-09-02 14:29                       ` Alan Modra
2020-09-02 14:35                         ` H.J. Lu
2020-09-03  1:31                           ` Alan Modra
2020-09-03  2:16                             ` H.J. Lu
2020-09-03  6:07                               ` Alan Modra
2020-09-03 11:34                                 ` H.J. Lu
2020-09-04  7:25                                   ` Alan Modra
2020-09-04 11:06                                     ` H.J. Lu
2020-09-08  5:42                                       ` Alan Modra
2020-09-08 12:43                                         ` 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=20200828015847.GG15695@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).