From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/2] Resolver-related libpthread cleanups
Date: Fri, 23 Apr 2021 09:48:47 -0700 [thread overview]
Message-ID: <CAMe9rOroNOKKWkhCzRpibeaR8AxitEzAryN+uS-djj1u_LzcUg@mail.gmail.com> (raw)
In-Reply-To: <cover.1619182587.git.fweimer@redhat.com>
On Fri, Apr 23, 2021 at 8:17 AM Florian Weimer via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Ip lan to push this shortly because I think it's non-controversial and
> it's more network-related than thread-related.
>
> __errno_location should receive the same treatment, but there could be
> references from assembler code, so I think it's best to delay that until
> all code is gone from libpthread.
>
> Tested on i686-linux-gnu and x86_64-linux-gnu. Built with
> build-many-glibcs.py.
>
> Thanks,
> Florian
>
> Florian Weimer (2):
> nptl: Remove __res_state from libpthread
> nptl: Remove __h_errno_location from libpthread
>
> nptl/Makefile | 2 --
> nptl/Versions | 2 --
> nptl/herrno.c | 34 -------------------
> nptl/res.c | 26 --------------
> .../sysv/linux/aarch64/libpthread.abilist | 2 --
> .../unix/sysv/linux/alpha/libpthread.abilist | 2 --
> .../unix/sysv/linux/arc/libpthread.abilist | 2 --
> .../unix/sysv/linux/arm/be/libpthread.abilist | 2 --
> .../unix/sysv/linux/arm/le/libpthread.abilist | 2 --
> .../unix/sysv/linux/csky/libpthread.abilist | 2 --
> .../unix/sysv/linux/hppa/libpthread.abilist | 2 --
> .../unix/sysv/linux/i386/libpthread.abilist | 2 --
> .../unix/sysv/linux/ia64/libpthread.abilist | 2 --
> .../linux/m68k/coldfire/libpthread.abilist | 2 --
> .../sysv/linux/m68k/m680x0/libpthread.abilist | 2 --
> .../linux/microblaze/be/libpthread.abilist | 2 --
> .../linux/microblaze/le/libpthread.abilist | 2 --
> .../sysv/linux/mips/mips32/libpthread.abilist | 2 --
> .../sysv/linux/mips/mips64/libpthread.abilist | 2 --
> .../unix/sysv/linux/nios2/libpthread.abilist | 2 --
> .../powerpc/powerpc32/libpthread.abilist | 2 --
> .../powerpc/powerpc64/be/libpthread.abilist | 2 --
> .../powerpc/powerpc64/le/libpthread.abilist | 2 --
> .../sysv/linux/riscv/rv32/libpthread.abilist | 2 --
> .../sysv/linux/riscv/rv64/libpthread.abilist | 2 --
> .../linux/s390/s390-32/libpthread.abilist | 2 --
> .../linux/s390/s390-64/libpthread.abilist | 2 --
> .../unix/sysv/linux/sh/be/libpthread.abilist | 2 --
> .../unix/sysv/linux/sh/le/libpthread.abilist | 2 --
> .../linux/sparc/sparc32/libpthread.abilist | 2 --
> .../linux/sparc/sparc64/libpthread.abilist | 2 --
> .../sysv/linux/x86_64/64/libpthread.abilist | 2 --
> .../sysv/linux/x86_64/x32/libpthread.abilist | 2 --
> 33 files changed, 122 deletions(-)
> delete mode 100644 nptl/herrno.c
> delete mode 100644 nptl/res.c
>
> --
> 2.30.2
>
LGTM.
Thanks.
--
H.J.
prev parent reply other threads:[~2021-04-23 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 12:58 [PATCH 0/2] Resolver-related libpthread cleanups Florian Weimer via Libc-alpha
2021-04-23 12:58 ` [PATCH 1/2] nptl: Remove __res_state from libpthread Florian Weimer via Libc-alpha
2021-04-23 12:58 ` [PATCH 2/2] nptl: Remove __h_errno_location " Florian Weimer via Libc-alpha
2021-04-23 16:48 ` H.J. Lu via Libc-alpha [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMe9rOroNOKKWkhCzRpibeaR8AxitEzAryN+uS-djj1u_LzcUg@mail.gmail.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--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).