From: Joseph Myers <joseph@codesourcery.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Cc: Matheus Castanho <msc@linux.ibm.com>,
Carlos O'Donell <carlos@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH] Update powerpc libm-test-ulps
Date: Tue, 1 Sep 2020 17:31:27 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2009011726480.6258@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87eenmaey3.fsf@linux.ibm.com>
On Mon, 31 Aug 2020, Tulio Magno Quites Machado Filho via Libc-alpha wrote:
> > 2. Do (1) only for entries that have ULPs higher than a threshold (say,
> > 9 or 16)?
>
> Likewise, if we're able to keep maximum ULPs at 9 without marking too many tests
> as xfail'ed, that's better.
> Per the contents of sysdeps/powerpc/fpu/libm-test-ulps, this should be possible
> and would not need have a greater max_valid_error for inexact functions just
> for ibm128.
If the functions for different floating-point formats use similar
algorithms, the error may be a multiple of the error for the basic
arithmetic operations. Since the basic arithmetic operations for
ldbl-128ibm are less accurate than for IEEE formats, it seems reasonable
to allow larger errors for libm functions for that format as well.
Ideally the errors would be smaller than they are for some functions with
larger errors, but that might require algorithmic improvements. The
existing bounds of 9 or 16 ulps are empirical, based on what's seen with
functions where the issue is simply the accumulation of lots of separate
errors rather than algorithms with inherent numerical problems.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-09-01 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 18:37 Matheus Castanho
2020-08-20 18:39 ` Carlos O'Donell
2020-08-20 18:56 ` Adhemerval Zanella
2020-08-20 19:44 ` Tulio Magno Quites Machado Filho
2020-08-20 21:25 ` Carlos O'Donell
2020-08-31 12:46 ` Matheus Castanho
2020-08-31 17:43 ` Tulio Magno Quites Machado Filho
2020-09-01 17:31 ` Joseph Myers [this message]
2020-09-02 14:52 ` Patsy Griffin
2020-08-20 19:00 ` Paul Zimmermann
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=alpine.DEB.2.21.2009011726480.6258@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msc@linux.ibm.com \
--cc=tuliom@linux.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).