From: "H.J. Lu" <hjl.tools@gmail.com>
To: Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/3] New generic sincosf
Date: Fri, 15 Dec 2017 14:32:00 -0000 [thread overview]
Message-ID: <CAMe9rOoTqhZeQd5iyfNhHtNWpoadxuh--W8XU=CVDLEV1h7xfg@mail.gmail.com> (raw)
In-Reply-To: <1e627de2-222e-0096-143e-bf987f572b1d@linux.vnet.ibm.com>
On Fri, Dec 15, 2017 at 6:17 AM, Rajalakshmi Srinivasaraghavan
<raji@linux.vnet.ibm.com> wrote:
>
>
> On 12/15/2017 07:49 AM, H.J. Lu wrote:
>>
>> On Thu, Dec 14, 2017 at 4:29 PM, Joseph Myers <joseph@codesourcery.com>
>> wrote:
>>>
>>> On Wed, 13 Dec 2017, Rajalakshmi Srinivasaraghavan wrote:
>>>
>>>> This implementation is based on generic s_sinf.c and s_cosf.c.
>>>> Tested on s390x, powerpc64le and powerpc32.
>>>>
>>>> 2017-12-12 Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>
>>>>
>>>> * sysdeps/ieee754/flt-32/s_cosf.c: Move reduced() and
>>>> constants to s_sincos.h file.
>>>> * sysdeps/ieee754/flt-32/s_sinf.c: Likewise.
>>>> * sysdeps/ieee754/flt-32/s_sincosf.c: New implementation.
>>>> * sysdeps/ieee754/flt-32/s_sincos.h: New file.
>>>
>>>
>>> OK.
>>>
>>
>> Please put those static constants into a different file and mark them
>> hidden so that they can be shared when they are compiled twice
>> for FMA.
>>
>
> I assume you are asking changes similar to
> sysdeps/ieee754/flt-32/e_exp2f_data.c. Could you please explain the
Yes.
On x86-64, I will compile sinf/cosf/sincosf twice, with and without FMA.
Both versions of sinf/cosf/sincosf should share the same set of
tables to avoid data duplication.
> advantage of doing this or suggest any previous mail thread which I can
> refer to?
Thanks.
--
H.J.
next prev parent reply other threads:[~2017-12-15 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 5:43 [PATCH 0/3] " Rajalakshmi Srinivasaraghavan
2017-12-13 5:43 ` [PATCH 3/3] s390: Update ulps Rajalakshmi Srinivasaraghavan
2017-12-13 5:43 ` [PATCH 1/3] New generic sincosf Rajalakshmi Srinivasaraghavan
2017-12-15 0:30 ` Joseph Myers
2017-12-15 2:19 ` H.J. Lu
2017-12-15 14:17 ` Rajalakshmi Srinivasaraghavan
2017-12-15 14:32 ` H.J. Lu [this message]
2017-12-15 14:33 ` Joseph Myers
2017-12-15 15:26 ` H.J. Lu
2017-12-15 15:48 ` Joseph Myers
2017-12-15 16:08 ` H.J. Lu
2017-12-15 16:24 ` Joseph Myers
2017-12-15 16:34 ` H.J. Lu
2017-12-15 20:34 ` H.J. Lu
2017-12-15 20:50 ` Joseph Myers
2017-12-16 8:53 ` Rajalakshmi Srinivasaraghavan
2017-12-16 14:43 ` H.J. Lu
2017-12-18 3:26 ` Rajalakshmi Srinivasaraghavan
2017-12-19 16:35 ` H.J. Lu
2018-01-01 10:16 ` Rajalakshmi Srinivasaraghavan
2017-12-13 5:43 ` [PATCH 2/3] powerpc: Update ulps Rajalakshmi Srinivasaraghavan
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='CAMe9rOoTqhZeQd5iyfNhHtNWpoadxuh--W8XU=CVDLEV1h7xfg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=raji@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).