From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Subject: Re: [PATCH v2] Add libm_alias_finite for _finite symbols
Date: Thu, 2 Jan 2020 13:28:20 +0530 [thread overview]
Message-ID: <e69e4baf-62b1-ead8-1fcf-3583c184ec4d@gotplt.org> (raw)
In-Reply-To: <20191021174548.25467-1-adhemerval.zanella@linaro.org>
On 21/10/19 11:15 pm, Adhemerval Zanella wrote:
> From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
>
> Sending on behalf of Wilco. Changes from previous version:
>
> - Fixed various missing compat symbols for i386, x86_64 and m68k.
>
> - Created libm-alias-finite.h which defines the libm_alias_finite
> macro that wraps the logic required to define the compat finite
> symbol.
>
> - Redefine declare_mgen_finite_alias_x as libm_alias_finite.
>
> - Adjusted for some non-existent files (powerpc exp multiarch).
>
> --
>
> This patch adds a new macro, libm_alias_finite, to define all _finite
> symbol. It sets all _finite symbol as compat symbol based on its first
> version (obtained from the definition at built generated first-versions.h).
>
> The <fn>f128_finite symbols were introduced in GLIBC 2.26 and so need
> special treatment in code that is shared between long double and float128.
> It is done by adding a list, similar to internal symbol redifinition,
> on sysdeps/ieee754/float128/float128_private.h.
>
> Alpha also needs some tricky changes to ensure we still emit 2 compat
> symbols for sqrt(f).
>
> Passes buildmanyglibc.
>
> Co-authored-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
This looks OK to me with the following changes:
1. Change SHLIB_COMPAT call to use 2_31 in libm-alias-finite.h and in
the alpha files
2. Update year in the copyright header.
Siddhesh
prev parent reply other threads:[~2020-01-02 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 17:45 [PATCH v2] Add libm_alias_finite for _finite symbols Adhemerval Zanella
2019-10-21 22:47 ` Joseph Myers
2019-10-22 12:44 ` Adhemerval Zanella
2020-01-02 7:58 ` 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
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=e69e4baf-62b1-ead8-1fcf-3583c184ec4d@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.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).