From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PING][PATCH 0/2] math symbols cleanup
Date: Mon, 22 Mar 2021 10:06:38 +0530 [thread overview]
Message-ID: <81562870-69d4-5e4a-94c6-4d6f06a13add@sourceware.org> (raw)
In-Reply-To: <20210211101908.2825685-1-siddhesh@sourceware.org>
Ping! Paul has tested [2/2] and Florian has reviewed the abilist files.
Can someone please review the macro soup and ack the series?
Thanks,
Siddhesh
On 2/11/21 3:49 PM, Siddhesh Poyarekar via Libc-alpha wrote:
> This patchset cleans up state of functions shared between libc and libm
> so that they're consistent and avoid duplication where possible.
>
> Siddhesh Poyarekar (2):
> Move __isnanf128 to libc.so
> Avoid adding duplicated symbols into static libraries
>
> math/Makefile | 3 +++
> sysdeps/ieee754/float128/Versions | 2 +-
> sysdeps/mach/hurd/i386/libc.abilist | 1 +
> sysdeps/mach/hurd/i386/libm.abilist | 1 -
> sysdeps/unix/sysv/linux/i386/libc.abilist | 1 +
> sysdeps/unix/sysv/linux/i386/libm.abilist | 1 -
> sysdeps/unix/sysv/linux/ia64/libc.abilist | 1 +
> sysdeps/unix/sysv/linux/ia64/libm.abilist | 1 -
> sysdeps/unix/sysv/linux/powerpc/powerpc64/le/libc.abilist | 1 +
> sysdeps/unix/sysv/linux/powerpc/powerpc64/le/libm.abilist | 1 -
> sysdeps/unix/sysv/linux/x86_64/64/libc.abilist | 1 +
> sysdeps/unix/sysv/linux/x86_64/64/libm.abilist | 1 -
> sysdeps/unix/sysv/linux/x86_64/x32/libc.abilist | 1 +
> sysdeps/unix/sysv/linux/x86_64/x32/libm.abilist | 1 -
> 14 files changed, 10 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2021-03-22 4:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 10:19 [PATCH " Siddhesh Poyarekar
2021-02-11 10:19 ` [PATCH 1/2] Move __isnanf128 to libc.so Siddhesh Poyarekar
2021-02-11 10:27 ` Florian Weimer
2021-02-11 14:14 ` [PATCH v2 " Siddhesh Poyarekar
2021-02-11 16:03 ` Florian Weimer
2021-03-29 13:57 ` Siddhesh Poyarekar
2021-03-29 22:02 ` Tulio Magno Quites Machado Filho
2021-03-30 9:31 ` [COMMITTED] " Siddhesh Poyarekar
2021-02-11 10:19 ` [PATCH 2/2] Avoid adding duplicated symbols into static libraries Siddhesh Poyarekar
2021-03-30 19:47 ` Adhemerval Zanella
2021-03-31 2:57 ` Siddhesh Poyarekar
2021-03-31 13:54 ` Tulio Magno Quites Machado Filho
2021-03-31 14:05 ` Siddhesh Poyarekar
2021-03-02 6:09 ` [PING][PATCH 0/2] math symbols cleanup Siddhesh Poyarekar
2021-03-22 4:36 ` Siddhesh Poyarekar [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=81562870-69d4-5e4a-94c6-4d6f06a13add@sourceware.org \
--to=siddhesh@sourceware.org \
--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).