public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jeevitha at linux dot ibm.com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/31818] New: math/test-float128-log2p1, math/test-float64x-log2p1, math/test-ldouble-log2p1 fails on ppc64le-power8-nomultiarch Date: Thu, 30 May 2024 09:26:41 +0000 [thread overview] Message-ID: <bug-31818-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31818 Bug ID: 31818 Summary: math/test-float128-log2p1, math/test-float64x-log2p1, math/test-ldouble-log2p1 fails on ppc64le-power8-nomultiarch Product: glibc Version: 2.39 Status: UNCONFIRMED Severity: normal Priority: P2 Component: math Assignee: unassigned at sourceware dot org Reporter: jeevitha at linux dot ibm.com Target Milestone: --- Log2p1 was implemented in commit id(79c52daf4740b00bef43e4f5a4281b3480459b38)and maximum allowed error was updated for powerpc in the commit (f83e461f1014598a5cb4c89407ce303b9f0bd8ac). We are seeing the tests was failing with "--disable-multi-arch" in power8 LE. The issue with those test cases is that the expected ULP from "sysdeps/powerpc/fpu/libm-test-ulps" does not match the result. The expected ULP for float128 is 2, but we are getting 3 for Power8. However, there are no issues on Power9 and Power10 since their output has error of 2 ulp. Can we change the ulps for float128 to 3? Is this a reasonable change. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-05-30 9:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-30 9:26 jeevitha at linux dot ibm.com [this message] 2024-05-30 9:30 ` [Bug math/31818] " jeevitha at linux dot ibm.com 2024-05-30 9:31 ` jeevitha at linux dot ibm.com 2024-05-30 9:32 ` jeevitha at linux dot ibm.com 2024-05-30 10:21 ` schwab@linux-m68k.org 2024-05-30 17:23 ` jsm28 at gcc dot gnu.org 2024-06-06 14:42 ` bergner at linux dot ibm.com 2024-06-21 10:18 ` jeevitha at linux dot ibm.com
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=bug-31818-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).