public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael.hudson at canonical dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/29463] New: math/test-float128-y1 fails on x86_64 Date: Tue, 09 Aug 2022 10:48:04 +0000 [thread overview] Message-ID: <bug-29463-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29463 Bug ID: 29463 Summary: math/test-float128-y1 fails on x86_64 Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: math Assignee: unassigned at sourceware dot org Reporter: michael.hudson at canonical dot com Target Milestone: --- Building glibc 2.36 on Ubuntu 22.10 using gcc 12 fails like so: FAIL: math/test-float128-y1 original exit status 1 testing _Float128 (without inline functions) Failure: Test: y1_downward (0x1.c1badep+0) Result: is: -2.49850711930108135145795303826944004e-01 -0x1.ffb1bae4fa20118544b142160f5fp-3 should be: -2.49850711930108135145795303826943836e-01 -0x1.ffb1bae4fa20118544b142160f58p-3 difference: 1.68518870133883137142398069976181140e-34 0x1.c000000000000000000000000000p-113 ulp : 7.0000 max.ulp : 5.0000 Maximal error of `y1_downward' is : 7 ulp accepted: 5 ulp Test suite completed: 216 test cases plus 212 tests for exception flags and 212 tests for errno executed. 2 errors occurred. I'm reasonably confident but not yet certain that building with gcc 11 works. I see that fedora 37 built glibc 2.36 with gcc 12 without hitting this issue, so it's possible it's the result of some Ubuntu-specific gcc issue but I'm not really sure. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-08-09 10:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-09 10:48 michael.hudson at canonical dot com [this message] 2022-08-09 22:29 ` [Bug math/29463] " michael.hudson at canonical dot com 2022-08-09 22:32 ` michael.hudson at canonical dot com 2022-08-10 21:14 ` michael.hudson at canonical dot com 2022-10-24 14:01 ` cvs-commit at gcc dot gnu.org 2022-10-24 15:32 ` adhemerval.zanella at linaro dot org 2022-10-24 18:57 ` cvs-commit at gcc dot gnu.org
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-29463-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).