From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Carlos O'Donell <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Cc: nd@arm.com, Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH 00/10] Optimized math routines
Date: Fri, 06 Jul 2018 15:46:00 -0000 [thread overview]
Message-ID: <b1105e5c-63e8-4edc-82f4-a986d1450961@arm.com> (raw)
In-Reply-To: <50b1b8b6-d03c-224f-31ff-8cf9d8268b6d@redhat.com>
On 06/07/18 13:43, Carlos O'Donell wrote:
> On 07/06/2018 04:47 AM, Szabolcs Nagy wrote:
>> Optimized exp, exp2, log, log2, pow, sinf, cosf and sincosf
>> implementations.
>
> Is it your intent to have these included in 2.28?
>
(resending as my previous mail seems to be lost)
yes, i'd like to add it to the 'desirable in 2.28' list
if Joseph is ok with the code, but i see he is not available
right now for review.
i don't know how other maintainers feel about such change,
there needs to be an ulp update (i'm willing to do that for
targets i can access hw for testing).
next prev parent reply other threads:[~2018-07-06 15:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:49 Szabolcs Nagy
2018-07-06 8:57 ` [PATCH 02/10] Improve performance of sincosf Szabolcs Nagy
2018-07-11 13:22 ` Szabolcs Nagy
2018-08-07 20:11 ` Joseph Myers
2018-08-10 12:12 ` Wilco Dijkstra
2018-08-10 16:04 ` Joseph Myers
2018-07-06 8:57 ` [PATCH 01/10] Clean up converttoint handling and document the semantics Szabolcs Nagy
2018-08-07 19:52 ` Joseph Myers
2018-07-06 8:59 ` [PATCH 03/10] Improve performance of sinf and cosf Szabolcs Nagy
2018-08-13 19:46 ` Joseph Myers
2018-08-14 19:41 ` Joseph Myers
2018-08-15 13:11 ` Wilco Dijkstra
2018-07-06 9:02 ` [PATCH 04/10] Add new exp and exp2 implementations Szabolcs Nagy
2018-08-22 19:55 ` Joseph Myers
2018-09-05 15:26 ` Szabolcs Nagy
2018-07-06 9:04 ` [PATCH 05/10] aarch64: update libm-test-ulps Szabolcs Nagy
2018-08-24 17:09 ` Joseph Myers
2018-07-06 9:05 ` [PATCH 06/10] arm: " Szabolcs Nagy
2018-07-06 9:06 ` [PATCH 07/10] x86_64: " Szabolcs Nagy
2018-07-06 9:08 ` [PATCH 08/10] Add new log implementation Szabolcs Nagy
2018-08-24 17:19 ` Joseph Myers
2018-07-06 9:09 ` [PATCH 09/10] Add new log2 implementation Szabolcs Nagy
2018-07-06 9:10 ` [PATCH 10/10] Add new pow implementation Szabolcs Nagy
2018-07-11 13:24 ` Szabolcs Nagy
2018-07-06 12:43 ` [PATCH 00/10] Optimized math routines Carlos O'Donell
2018-07-06 15:46 ` Szabolcs Nagy [this message]
2018-07-06 16:27 ` Carlos O'Donell
2018-07-06 17:17 ` Szabolcs Nagy
2018-07-09 12:15 ` Szabolcs Nagy
2018-07-09 13:09 ` Adhemerval Zanella
2018-07-09 13:35 ` Szabolcs Nagy
2018-07-09 14:27 ` Adhemerval Zanella
2018-07-09 15:41 ` Szabolcs Nagy
2018-07-09 18:20 ` Adhemerval Zanella
2018-07-17 21:59 ` Joseph Myers
2018-07-18 0:07 ` Carlos O'Donell
2018-07-11 13:39 ` Szabolcs Nagy
2018-07-11 14:19 ` [PATCH] powerpc: update libm-test-ulps Szabolcs Nagy
2018-07-12 15:52 ` [PATCH] update libm-test-ulps for new exp Szabolcs Nagy
2018-07-18 17:25 ` Joseph Myers
2018-07-19 9:15 ` Szabolcs Nagy
2018-07-19 17:03 ` Joseph Myers
2018-07-19 17:15 ` Wilco Dijkstra
2018-07-19 17:23 ` Joseph Myers
2018-08-07 11:03 ` [PATCH 00/10] Optimized math routines Szabolcs Nagy
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=b1105e5c-63e8-4edc-82f4-a986d1450961@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).