public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: libc-alpha@sourceware.org, carlos@redhat.com
Subject: Re: New math test failures on Fedora/33
Date: Mon, 18 Jan 2021 15:36:30 +0100	[thread overview]
Message-ID: <mwsg6y2txt.fsf@tomate.loria.fr> (raw)
In-Reply-To: <VE1PR08MB5599C33918BBFC600FC3350383A40@VE1PR08MB5599.eurprd08.prod.outlook.com> (message from Wilco Dijkstra via Libc-alpha on Mon, 18 Jan 2021 14:22:50 +0000)

       Dear Wilco,

> On the subject of ULPs, how about centralizing the ULP files into a single
> generic file and only adding entries to target ULP files for special cases?
> More of the math functions are becoming generic and so the ULPs should be
> the same for most (some entries might need fma and non-fma variants of course).
> Then you only need the target versions for special cases like non-standard IEEE
> formats, target specific implementations with different ULPs etc.
> 
> And if there aren't that many special cases you could use a single file with
> a syntax like:
> 
> Function: "acos":
> float: 1            // generic case
> float-alpha: 2

good idea! One question: when one does "make regen-ulps", how would it know which
value to update? For each function, we would need to tag it as "generic" or not on
each target?

By the way, "make regen-ulps" gives a diff if the new ulps are larger, but does it
also when the new ulps are smaller (for example if we improved the algorithm)?

Paul

  reply	other threads:[~2021-01-18 14:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 14:22 Wilco Dijkstra
2021-01-18 14:36 ` Paul Zimmermann [this message]
2021-01-18 14:36 ` Andreas Schwab
2021-01-18 15:18   ` Paul Zimmermann
2021-01-18 17:03     ` Andreas Schwab
2021-01-18 15:20   ` Wilco Dijkstra
2021-01-18 15:30     ` Carlos O'Donell
2021-01-18 15:38       ` Andreas Schwab
2021-01-18 16:58 ` Florian Weimer
2021-01-19 15:59 ` Patrick McGehearty
  -- strict thread matches above, loose matches on Subject: below --
2021-01-11 16:00 H.J. Lu
2021-01-11 16:28 ` Adhemerval Zanella
2021-01-11 18:37   ` H.J. Lu
2021-01-11 19:21     ` Adhemerval Zanella
2021-01-12  7:13       ` Paul Zimmermann
2021-01-12 17:29         ` Adhemerval Zanella
2021-01-12 17:39           ` Siddhesh Poyarekar
2021-01-12 19:14           ` Tulio Magno Quites Machado Filho
2021-01-13  6:34             ` Paul Zimmermann
2021-01-13 12:51               ` Adhemerval Zanella
2021-01-14 12:48                 ` Carlos O'Donell
2021-01-14 12:59             ` Carlos O'Donell
2021-01-14 13:19               ` Paul Zimmermann
2021-01-14 14:47                 ` Carlos O'Donell
2021-01-14 13:07 ` Carlos O'Donell

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=mwsg6y2txt.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=carlos@redhat.com \
    --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).