From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: libc-alpha@sourceware.org, carlos@redhat.com
Subject: Re: [PATCH v2 1/2] Move __isnanf128 to libc.so
Date: Thu, 11 Feb 2021 17:03:21 +0100 [thread overview]
Message-ID: <87o8gqoaly.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210211141447.2970749-1-siddhesh@sourceware.org> (Siddhesh Poyarekar's message of "Thu, 11 Feb 2021 19:44:47 +0530")
* Siddhesh Poyarekar:
> All of the isnan functions are in libc.so due to printf_fp, so move
> __isnanf128 there too for consistency.
I can't comment on the mechanics to get there, but the result looks as
expected to me.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2021-02-11 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 10:19 [PATCH 0/2] math symbols cleanup 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 [this message]
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
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=87o8gqoaly.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).