public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.hudson at canonical dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106574] New: gcc 12 with O3 leads to failures in glibc's y1f128 tests
Date: Tue, 09 Aug 2022 22:54:05 +0000	[thread overview]
Message-ID: <bug-106574-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106574

            Bug ID: 106574
           Summary: gcc 12 with O3 leads to failures in glibc's y1f128
                    tests
           Product: gcc
           Version: 12.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: michael.hudson at canonical dot com
  Target Milestone: ---

Initially reported here, but more likely to be a gcc issue: if I build glibc
with gcc 12 and -O3 (as is the default in Debian/Ubuntu) I get this failure:

(kinetic-amd64)root@anduril:/build/glibc-EA2Jch/glibc-2.36/build-tree/amd64-libc#
./elf/ld-linux-x86-64.so.2 --library-path .:./elf:./math 
./math/test-float128-y1
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.

Building the e_j1f128.os object with -O2 or with gcc-11 fixes the failure.

Not sure how to reduce this to a smaller test case, but I'm happy to try
things.

             reply	other threads:[~2022-08-09 22:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 22:54 michael.hudson at canonical dot com [this message]
2022-08-09 23:12 ` [Bug target/106574] " michael.hudson at canonical dot com
2022-08-09 23:15 ` pinskia at gcc dot gnu.org
2022-08-09 23:18 ` michael.hudson at canonical dot com
2022-08-10  7:25 ` rguenth at gcc dot gnu.org
2022-08-10 14:58 ` joseph at codesourcery dot com
2022-08-10 21:26 ` michael.hudson at canonical dot com
2022-08-10 22:25 ` joseph at codesourcery dot com
2022-08-10 22:49 ` michael.hudson at canonical dot com
2022-08-10 22:54 ` michael.hudson at canonical dot com
2022-08-10 23:27 ` michael.hudson at canonical dot com
2022-08-11 20:34 ` joseph at codesourcery dot com
2022-08-11 21:36 ` michael.hudson at canonical dot com
2022-09-06 22:07 ` michael.hudson at canonical dot com
2022-09-06 22:14 ` pinskia 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-106574-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).