public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Wilco Dijkstra via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: New math test failures on Fedora/33
Date: Mon, 18 Jan 2021 15:20:06 +0000	[thread overview]
Message-ID: <VE1PR08MB5599E624AFCF9CFA7D1DDEA983A40@VE1PR08MB5599.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <877doal3be.fsf@igel.home>

Hi Andreas,

>> 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?
>
> How about ditching the ULP files altogether?  Why can't we just
> generally accept the maximum valid ULP everywhere?

Yes that is possible, and that should remove all the annoying ULP file maintenance.
I think the maximum is 10 ULP currently, so if we accepted that for all math functions
then ULP testing would be almost useless. However we could set a target for each
function using a generic ULP file. Then the ULP checker would give a warning if the ULP
is larger (so each target generates a short list of cases that could be improved). If ULP is
larger than some maximum (which could be set per math function) you would get the
existing error.

Cheers,
Wilco

  parent reply	other threads:[~2021-01-18 15:20 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
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 [this message]
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=VE1PR08MB5599E624AFCF9CFA7D1DDEA983A40@VE1PR08MB5599.eurprd08.prod.outlook.com \
    --to=wilco.dijkstra@arm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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).