From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [COMMITTED] arm: update libm test ulps
Date: Tue, 13 Apr 2021 10:52:14 +0100 [thread overview]
Message-ID: <20210413095214.GV23289@arm.com> (raw)
In-Reply-To: <ace9fd0a-6c0a-5397-b48e-c3c6d09570db@synopsys.com>
The 04/11/2021 18:04, Vineet Gupta wrote:
> On 4/8/21 1:58 AM, Szabolcs Nagy via Libc-alpha wrote:
> > Updated after commits 9acda61d94acc5348c2330f2519a14d1a4a37e73
> > and 43576de04afc6a0896a3ecc094e1581069a0652a.
>
> Is there a better way for this to be done at the time of original change
> other than running the tests on all affected architectures. arches
> always seem to be chasing these kind of changes ...
i think there are only small variations between targets for
float and double, so the ulp error limits for those could be
shared (unless a target has its own implementation with
different quality requirement for some reason).
long double is more target specific. i think the tests could
be organised such that each sysdeps/ieee754/* directory has
its own ulp limits file and the target picks up the right one.
and libmvec needs target specific ulp limits.
i don't know how hard it would be to implement this.
next prev parent reply other threads:[~2021-04-13 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:58 Szabolcs Nagy
2021-04-11 18:04 ` Vineet Gupta
2021-04-13 9:52 ` Szabolcs Nagy [this message]
2021-04-13 15:01 ` Adhemerval Zanella
2021-04-13 18:02 ` Joseph Myers
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=20210413095214.GV23289@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.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).