public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95450] New: [10 regression] Wrong long double folding Date: Sun, 31 May 2020 12:51:24 +0000 [thread overview] Message-ID: <bug-95450-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95450 Bug ID: 95450 Summary: [10 regression] Wrong long double folding Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: schwab@linux-m68k.org Target Milestone: --- Target: powerpc-*.* $ cat test-float.c #include <float.h> #include <assert.h> union gl_long_double_union { struct { double hi; double lo; } dd; long double ld; }; const union gl_long_double_union gl_LDBL_MAX = { { DBL_MAX, DBL_MAX / (double)134217728UL / (double)134217728UL } }; # undef LDBL_MAX # define LDBL_MAX (gl_LDBL_MAX.ld) int main () { volatile long double m = LDBL_MAX; assert (m + m > m); } $ gcc -O2 test-float.c $ ./a.out a.out: test-float.c:20: main: Assertion `m + m > m' failed. Aborted test-float.c.234t.optimized contains: m ={v} 1.79769313486231580793728971405302307166001572487e+308; but that evaluates to Inf. DBL_MAX is 1.79769313486231570814527423731704e+308L.
next reply other threads:[~2020-05-31 12:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-31 12:51 schwab@linux-m68k.org [this message] 2020-06-02 7:32 ` [Bug target/95450] [10/11 " rguenth at gcc dot gnu.org 2020-06-02 8:34 ` schwab@linux-m68k.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-08-11 16:14 ` carlos at redhat dot com 2020-08-11 16:17 ` mpolacek at gcc dot gnu.org 2020-08-11 16:19 ` jakub at gcc dot gnu.org 2020-08-11 16:46 ` jakub at gcc dot gnu.org 2020-08-11 16:54 ` jakub at gcc dot gnu.org 2020-08-11 17:26 ` jakub at gcc dot gnu.org 2020-08-25 5:18 ` cvs-commit at gcc dot gnu.org 2020-08-25 17:45 ` cvs-commit at gcc dot gnu.org 2020-08-25 18:25 ` jakub 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-95450-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: 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).