public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] riscv: Update nofpu libm test ulps Date: Mon, 18 Mar 2024 10:29:15 +0000 (GMT) [thread overview] Message-ID: <20240318102915.328E33858D1E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f44f3aed31a2d18dc1aa70fce8d466cf6e56b93c commit f44f3aed31a2d18dc1aa70fce8d466cf6e56b93c Author: Darius Rad <darius@bluespec.com> Date: Mon Mar 18 11:28:50 2024 +0100 riscv: Update nofpu libm test ulps Fix two test failures. Reviewed-by: Florian Weimer <fweimer@redhat.com> Diff: --- sysdeps/riscv/nofpu/libm-test-ulps | 1 + 1 file changed, 1 insertion(+) diff --git a/sysdeps/riscv/nofpu/libm-test-ulps b/sysdeps/riscv/nofpu/libm-test-ulps index 16106f10b0..bc7e615177 100644 --- a/sysdeps/riscv/nofpu/libm-test-ulps +++ b/sysdeps/riscv/nofpu/libm-test-ulps @@ -1043,6 +1043,7 @@ ldouble: 8 Function: "hypot": double: 1 +float: 1 ldouble: 1 Function: "hypot_downward":
next reply other threads:[~2024-03-18 10:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-18 10:29 Florian Weimer [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-07-27 13:51 Adhemerval Zanella
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=20240318102915.328E33858D1E@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).