From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/6] Prepare redirections for IEEE long double on powerpc64le
Date: Tue, 11 Feb 2020 15:25:08 -0300 [thread overview]
Message-ID: <87k14tt20r.fsf@linux.ibm.com> (raw)
In-Reply-To: <e45cc7364378680bab99a6cd6c5608bd3f5a0acc.1580757509.git.murphyp@linux.vnet.ibm.com>
"Paul E. Murphy" <murphyp@linux.vnet.ibm.com> writes:
> All functions that have a format string, which can consume a long double
> argument, must have one version for each long double format supported on
> a platform. On powerpc64le, these functions currently have two versions
> (i.e.: long double with the same format as double, and long double with
> IBM Extended Precision format). Support for a third long double format
> option (i.e. long double with IEEE long double format) is being prepared
> and all the aforementioned functions now have a third version (not yet
> exported on the master branch, but the code is in).
>
> For these functions to get selected (during build time), references to
> them in user programs (or dependent libraries) must get redirected to
> the aforementioned new versions of the functions. This patch installs
> the header magic required to perform such redirections.
>
> Notice, however, that since the redirections only happen when
> __LONG_DOUBLE_USES_FLOAT128 is set to 1, and no platform (including
> powerpc64le) currently does it, no redirections actually happen.
> Redirections and the exporting of the new functions will happen at the
> same time (when powerpc64le adds ldbl-128ibm-compat to their Implies.
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
--
Tulio Magno
next prev parent reply other threads:[~2020-02-11 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 21:10 [PATCH 0/6] long double to _Float128 redirecting support Paul E. Murphy
2020-02-03 21:10 ` [PATCH 1/6] Prepare redirections for IEEE long double on powerpc64le Paul E. Murphy
2020-02-10 21:32 ` Paul E Murphy
2020-02-17 14:34 ` Paul E Murphy
2020-02-18 14:27 ` Paul E Murphy
2020-02-11 18:25 ` Tulio Magno Quites Machado Filho [this message]
2020-02-03 21:10 ` [PATCH 2/6] Undefine redirections after long double definition on __LDBL_COMPAT [BZ #23294] Paul E. Murphy
2020-02-17 15:08 ` Paul E Murphy
2020-02-18 15:15 ` Paul E Murphy
2020-02-21 14:31 ` Paul E Murphy
2020-02-03 21:10 ` [PATCH 3/6] ldbl-128ibm-compat: Redirect long double functions to f128/ieee128 functions Paul E. Murphy
2020-02-24 14:58 ` Paul E Murphy
2020-02-28 14:55 ` Paul E Murphy
2020-02-03 21:10 ` [PATCH 4/6] ldbl-128ibm-compat: Redirect complex math functions Paul E. Murphy
2020-02-11 18:36 ` Tulio Magno Quites Machado Filho
2020-02-28 14:59 ` Paul E Murphy
2020-02-03 21:10 ` [PATCH 5/6] ldbl-128ibm-compat: Provide ieee128 symbols to narrow functions Paul E. Murphy
2020-02-18 22:23 ` Paul E Murphy
2020-02-21 14:29 ` Paul E Murphy
2020-02-03 21:10 ` [PATCH 6/6] Add a generic scalb implementation Paul E. Murphy
2020-02-11 20:20 ` Paul E Murphy
2020-02-12 1:21 ` Joseph Myers
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=87k14tt20r.fsf@linux.ibm.com \
--to=tuliom@ascii.art.br \
--cc=libc-alpha@sourceware.org \
--cc=murphyp@linux.vnet.ibm.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).