public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/323] optimized code gives strange floating point results Date: Wed, 31 Dec 2014 00:00:00 -0000 [thread overview] Message-ID: <bug-323-4-taYHqyoJbn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-323-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=323 --- Comment #197 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- (In reply to Manuel López-Ibáñez from comment #196) > Also, the official FAQ for this (https://gcc.gnu.org/bugs/#nonbugs_general) > is seriously lacking info and outdated. From now on, I'll point people to: > https://gcc.gnu.org/wiki/FAQ#PR323 Note that this bug was mainly about the excess precision of x87 FPU, though its summary just says "optimized code gives strange floating point results". But the users should be aware that the floating-point results can still depend on the optimization level because this is allowed by the ISO C standard. For instance, if one has code like x*y+z, a FMA can be used or not depending on the target architecture and the optimization level (see also bug 37845 about this), and this can change the results. >From gcc-bugs-return-471979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 31 00:03:14 2014 Return-Path: <gcc-bugs-return-471979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 8024 invoked by alias); 31 Dec 2014 00:03:14 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 7972 invoked by uid 48); 31 Dec 2014 00:03:10 -0000 From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/64447] [5 Regression] FAIL: gcc.dg/vect/slp-9.c Date: Wed, 31 Dec 2014 00:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: blocker X-Bugzilla-Who: hjl.tools at gmail dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-64447-4-S1T1t5gOOQ@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64447-4@http.gcc.gnu.org/bugzilla/> References: <bug-64447-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg02986.txt.bz2 Content-length: 864 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd447 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> --- I still see: FAIL: gcc.dg/vect/slp-9.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/vect/slp-9.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-9.c scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/vect/slp-9.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 with r219114: https://gcc.gnu.org/ml/gcc-testresults/2014-12/msg03418.html
next prev parent reply other threads:[~2014-12-31 0:00 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-323-4@http.gcc.gnu.org/bugzilla/> 2010-10-05 19:00 ` pinskia at gcc dot gnu.org 2011-01-13 22:10 ` pinskia at gcc dot gnu.org 2011-02-21 12:47 ` rguenth at gcc dot gnu.org 2011-03-08 19:11 ` acfbuerger at googlemail dot com 2011-03-22 16:14 ` rguenth at gcc dot gnu.org 2012-01-13 6:33 ` pinskia at gcc dot gnu.org 2012-04-24 8:23 ` rguenth at gcc dot gnu.org 2012-11-12 14:54 ` paolo.carlini at oracle dot com 2012-11-30 18:08 ` pinskia at gcc dot gnu.org 2012-12-15 2:10 ` soren.sandmann at gmail dot com 2012-12-31 16:13 ` rguenth at gcc dot gnu.org 2013-01-30 8:58 ` jakub at gcc dot gnu.org 2013-04-26 16:07 ` ondrej at sury dot org 2013-06-24 10:53 ` rguenth at gcc dot gnu.org 2013-11-18 18:47 ` dominiq at lps dot ens.fr 2014-01-02 8:35 ` Martin.vGagern at gmx dot net 2014-06-27 0:07 ` pinskia at gcc dot gnu.org 2014-12-30 18:45 ` manu at gcc dot gnu.org 2014-12-30 19:16 ` manu at gcc dot gnu.org 2014-12-31 0:00 ` vincent-gcc at vinc17 dot net [this message] 2014-12-31 0:45 ` manu at gcc dot gnu.org 2015-01-26 19:05 ` schwab@linux-m68k.org 2015-05-29 16:50 ` jsm28 at gcc dot gnu.org 2020-04-29 18:01 ` pinskia at gcc dot gnu.org 2021-05-31 3:46 ` pinskia at gcc dot gnu.org 2021-09-02 7:41 ` pinskia at gcc dot gnu.org 2021-10-27 7:55 ` jessicaking07 at protonmail dot com 2021-11-02 7:17 ` pinskia at gcc dot gnu.org 2021-11-05 23:18 ` timturnerc at yahoo dot com 2022-07-02 2:09 ` pinskia at gcc dot gnu.org 2022-10-14 7:32 ` cvs-commit at gcc dot gnu.org 2023-07-05 19:22 ` pinskia at gcc dot gnu.org 2023-07-05 20:15 ` vincent-gcc at vinc17 dot net 2023-07-05 21:00 ` vincent-gcc at vinc17 dot net 2023-07-11 8:25 ` malat at debian dot org 2023-09-21 13:34 ` pinskia at gcc dot gnu.org 2024-01-31 8:52 ` 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-323-4-taYHqyoJbn@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).