public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bregor@sf.anu.edu.au To: gcc-gnats@gcc.gnu.org Subject: optimization/8156: -mcpu=pentium4 generates wrong fp results in glibc-2.3 Date: Sun, 06 Oct 2002 20:06:00 -0000 [thread overview] Message-ID: <20021007030404.28934.qmail@sources.redhat.com> (raw) >Number: 8156 >Category: optimization >Synopsis: -mcpu=pentium4 generates wrong fp results in glibc-2.3 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sun Oct 06 20:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Roger Brown >Release: gcc (GCC) 3.2.1 20021004 (prerelease) >Organization: >Environment: Linux-2.4.19-pre10 HJL's binutils-2.13.90.0.4 glibc-2.3 release source code >Description: *** This may be a duplicate report but the original seems to have got lost. After building the released source for glibc-2.3, with "gcc (GCC) 3.2.1 20021004 (prerelease)", and the -mcpu=pentium4 -march=pentium4 switches, make check discovered many serious errors for the floating-point special functions (see below). The same build, with -mcpu=i686 -march=i686 failed with an assembler error. With -mcpu and -march left at the default values, both the build and check are clean. Other software details: O/S linux-2.4.19-pre10 and HJL's Linux-binutils-2.13.90.0.4. The actual "check" failure was: GCONV PATH=/Main/Glibc/glibc-2.3/Build/iconvdata LC ALL=C /Main/Glibc/glibc-2.3/Build/elf/ld-linux.so.2 --library-path /Main/Glibc/glibc-2.3/Build:/Main/Glibc/glibc-2.3/Build/math: /Main/Glibc/glibc-2.3/Build/elf:/Main/Glibc/glibc-2.3/Build/dlfcn: /Main/Glibc/glibc-2.3/Build/nss:/Main/Glibc/glibc-2.3/Build/nis: /Main/Glibc/glibc-2.3/Build/rt:/Main/Glibc/glibc-2.3/Build/resolv: /Main/Glibc/glibc-2.3/Build/crypt:/Main/Glibc/glibc-2.3/Build/linuxthreads /Main/Glibc/glibc-2.3/Build/math/test-idouble > /Main/Glibc/glibc-2.3/Build/math/test-idouble.out make[2]: *** [/Main/Glibc/glibc-2.3/Build/math/test-idouble.out] Error 139 The errors reported in test-idouble.out are alarming ! The first part reads: testing double (without inline functions) Failure: Test: cosh (0.75) == 1.29468328467684468784170818539018176 Result: is: 2.11700001661267478426e+00 0x1.0ef9db467dcf80000000p+1 should be: 1.29468328467684479222e+00 0x1.4b705d1e5d6a80000000p+0 difference: 8.22316731935829992040e-01 0x1.a506b2dd3c6900000000p-1 ulp : 3703385327526728.0000 max.ulp : 0.0000 Maximal error of `cosh' is : 3703385327526728 ulp accepted: 0 ulp Failure: sinh (-inf) == -inf: Exception "Invalid operation" set Failure: Test: sinh (-inf) == -inf Result: is: nan nan should be: -inf -inf Failure: Test: sinh (0.75) == 0.822316731935829980703661634446913849 and it gets much worse, much worse !! Specific *.i files etc can be provided. >How-To-Repeat: Build glibc-2.3 with -mcpu=pentium4 -march=pentium4 >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-07 3:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-06 20:06 bregor [this message] 2002-10-06 21:46 Andreas Jaeger 2002-10-07 4:16 Andreas Steinmetz 2002-10-07 4:56 Richard Henderson 2003-05-13 18:46 Dara Hazeghi 2003-05-14 10:27 giovannibajo
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=20021007030404.28934.qmail@sources.redhat.com \ --to=bregor@sf.anu.edu.au \ --cc=gcc-gnats@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: 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).