public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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: Mon, 09 Jul 2018 12:15:00 -0000	[thread overview]
Message-ID: <25ede414-21e9-bc19-c624-197c3435a346@arm.com> (raw)
In-Reply-To: <dc44c9c9-f4da-e160-36d7-b644ca64f0b1@arm.com>

On 06/07/18 18:17, Szabolcs Nagy wrote:
> On 06/07/18 17:27, Carlos O'Donell wrote:
>> On 07/06/2018 11:46 AM, Szabolcs Nagy wrote:
>>> 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).
>>
>> Where there any unanswered questions in your v4 review?
>>
>> Do you think v4 is basically as good as it will get?
>>
>> Who were the people who signed off on the review?
>>
> 
> Joseph Myers started the review of both the sinf, cosf, sincosf
> changes and the exp, exp2, log, log2, pow changes.
> 
> I think I addressed all of his comments in an acceptable way,
> but i don't know if he had other concerns or if parts of the
> code he has not reviewed yet.
> 
> Since the glibc tests pass on 3 different targets (and
> build-many-glibcs.py) i think there is no danger of the
> patch being completely broken.  Wilco and I tested the patches
> in detail outside of glibc so it is the glibc integration where
> I expected most of the issues.
> 
> I don't expect performance regression on any target, but it
> was not measured e.g. on powerpc (only aarch64 and x86_64)
> which might have different behaviour (previous sincosf was
> optimized on that target hence it might make sense to retest
> the new code to be sure).
> 
> I think the patches are in a good quality state now.
> (The ABI changing part needs further work so i didn't post that.)

built and tested on a power8 machine now, glibc math
tests pass (except for an unrelated fmal failure),
benchmark improvements are consistent with aarch64/x86_64,
but it was a shared access machine so i won't post exact
numbers, sincosf improved a bit too, sinf/cosf didn't
(apparently powerpc has its own implementation).

  reply	other threads:[~2018-07-09 12:15 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
2018-07-06 16:27     ` Carlos O'Donell
2018-07-06 17:17       ` Szabolcs Nagy
2018-07-09 12:15         ` Szabolcs Nagy [this message]
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=25ede414-21e9-bc19-c624-197c3435a346@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).