public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25615] dlopen RTLD_NOLOAD optimization
Date: Mon, 30 Mar 2020 16:47:52 +0000	[thread overview]
Message-ID: <bug-25615-131-S7HffPBoFh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25615-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25615

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com
   Last reconfirmed|                            |2020-03-30
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
At a glance I agree that this optimization seems to make sense. I haven't
thought too deeply about the consequences. Someone would have to ensure that
you could avoid calling _dl_map_object_deps and still get the intended link map
promotion effects and prove that with test cases that use RTLD_NOLOAD.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

       reply	other threads:[~2020-03-30 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-25615-131@http.sourceware.org/bugzilla/>
2020-03-30 16:47 ` carlos at redhat dot com [this message]
2024-03-13 20:27 ` conanhc at gmail dot com
2024-03-14 10:09 ` fweimer at redhat dot com

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=bug-25615-131-S7HffPBoFh@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).