public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 00/14] Move libdl into libc
Date: Sat, 22 May 2021 19:16:21 +0200	[thread overview]
Message-ID: <871r9y4rkq.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87o8d36gnn.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Fri, 21 May 2021 21:17:00 +0200")

* Florian Weimer via Libc-alpha:

> * Florian Weimer via Libc-alpha:
>
>> This patch series removes all code from libdl.so.2.  I have not removed
>> the shared object itself because I want to mirror what we are doing for
>> libpthread, and the discussion there is still ongoing.
>>
>> There is an oddity because for several targets, the baseline ABI version
>> for libdl is GLIBC_2.0 and not GLIBC_2.2.  This cannot be expressed with
>> the existing Versions framework.  Since the affected targets are more or
>> less on the way out anyway (hppa, ia64, sh, sparc64), I didn't
>> overdesign the solution and emitted the required version nodes directly
>> in scripts/versions.awk.
>>
>> This move also happens on Hurd because the implementation isn't
>> separate.
>>
>> This fixes a POSIX conformance issue with the c99 command because POSIX
>> requires that dlopen etc. are available without -ldl.
>>
>> Tested on i386-linux-gnu and x86_64-linux-gnu.  Built with
>> build-many-glibcs.py (including most intermediate steps).
>
> I should have mentioned that I'm removing the strange double-build with
> those dlfcn/sdl*.c files.  This is why the files have somewhat different
> layout after the move.  I do not see any value in the dlfcn/sdl*.c
> construct.  The new version relies on compiler inlining to remove
> redudant functions.

And I've pushed a rebase series to the fw/libdl branch.

Florian


      reply	other threads:[~2021-05-22 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 18:03 Florian Weimer
2021-05-19 18:04 ` [PATCH 01/14] stdio-common: Remove _IO_vfwscanf Florian Weimer
2021-05-19 18:04 ` [PATCH 02/14] Add libc ABI extension kludge for baseline-violating libdl symbols Florian Weimer
2021-05-19 18:04 ` [PATCH 03/14] dlfcn: Move dlerror into libc Florian Weimer
2021-05-19 18:04 ` [PATCH 04/14] dlfcn: Move dlclose " Florian Weimer
2021-05-19 18:04 ` [PATCH 05/14] dlfcn: Move dladdr " Florian Weimer
2021-05-19 18:04 ` [PATCH 06/14] dlfcn: Move dlsym " Florian Weimer
2021-05-19 18:04 ` [PATCH 07/14] dlfcn: Move dlmopen " Florian Weimer
2021-05-19 18:04 ` [PATCH 08/14] dlfcn: Move dladdr1 " Florian Weimer
2021-05-19 18:04 ` [PATCH 09/14] dlfcn: Move dlinfo " Florian Weimer
2021-05-19 18:05 ` [PATCH 10/14] dlfcn: Move dlvsym " Florian Weimer
2021-05-19 18:05 ` [PATCH 11/14] dlfcn: Move dlopen " Florian Weimer
2021-05-19 18:05 ` [PATCH 12/14] dlfcn: Cleanups after -ldl is no longer required Florian Weimer
2021-05-19 18:05 ` [PATCH 13/14] dlfcn: Eliminate GLIBC_PRIVATE dependency from tststatic2 Florian Weimer
2021-05-19 18:05 ` [PATCH 14/14] dlfcn: Rework static dlopen hooks Florian Weimer
2021-05-21 19:17 ` [PATCH 00/14] Move libdl into libc Florian Weimer
2021-05-22 17:16   ` Florian Weimer [this message]

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=871r9y4rkq.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@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).