From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>,
"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: Sun, 11 Apr 2021 18:04:36 +0000 [thread overview]
Message-ID: <ace9fd0a-6c0a-5397-b48e-c3c6d09570db@synopsys.com> (raw)
In-Reply-To: <20210408085827.5369-1-szabolcs.nagy@arm.com>
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 ...
> ---
> sysdeps/arm/libm-test-ulps | 50 +++++++++++++++++++-------------------
> 1 file changed, 25 insertions(+), 25 deletions(-)
>
> diff --git a/sysdeps/arm/libm-test-ulps b/sysdeps/arm/libm-test-ulps
> index cdb635ee3d..f7e6046da4 100644
> --- a/sysdeps/arm/libm-test-ulps
> +++ b/sysdeps/arm/libm-test-ulps
> @@ -851,35 +851,35 @@ double: 1
>
> Function: "j0":
> double: 2
> -float: 8
> +float: 9
>
> Function: "j0_downward":
> -double: 2
> -float: 4
> +double: 5
> +float: 9
[snip]
next prev parent reply other threads:[~2021-04-11 18:04 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 [this message]
2021-04-13 9:52 ` Szabolcs Nagy
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=ace9fd0a-6c0a-5397-b48e-c3c6d09570db@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@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).