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/34678] Optimization generates incorrect code with -frounding-math option (#pragma STDC FENV_ACCESS not implemented) Date: Fri, 10 Jan 2014 11:40:00 -0000 [thread overview] Message-ID: <bug-34678-4-vD4gdl4y2G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34678-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34678 --- Comment #24 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- (In reply to Nick Maclaren from comment #23) > If __STDC_IEC_559__ is unset or does not have the value 1, setting > STDC FENV_ACCESS to "on" is undefined behaviour (see 6.10.8.3, 7.6 and > Annex F), unless the implementation explicitly chooses to extend the > language to support it. You're wrong. The C standard doesn't say that. 6.10.8.3 says: "__STDC_IEC_559__ The integer constant 1, intended to indicate conformance to the specifications in annex F (IEC 60559 floating-point arithmetic)." and nothing about STDC FENV_ACCESS. In 7.6, only 7.6.1 is specifically about the FENV_ACCESS pragma, and it specifies under which conditions the behavior is undefined, but nothing related to __STDC_IEC_559__ and Annex F. Annex F doesn't apply in the case __STDC_IEC_559__ is unset. >From gcc-bugs-return-439939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 10 11:45:55 2014 Return-Path: <gcc-bugs-return-439939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 1214 invoked by alias); 10 Jan 2014 11:45:55 -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 1183 invoked by uid 48); 10 Jan 2014 11:45:52 -0000 From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59755] BUG Increment Operator with Accessing Arrays Date: Fri, 10 Jan 2014 11:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.8.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: <bug-59755-4-kCmWqtJijL@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59755-4@http.gcc.gnu.org/bugzilla/> References: <bug-59755-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-01/txt/msg01081.txt.bz2 Content-length: 793 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59755 Markus Trippelsdorf <trippels at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |trippels at gcc dot gnu.org Resolution|--- |INVALID --- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- With -Wall one gets: test.c: In function ‘main’: test.c:12:14: warning: operation on ‘m’ may be undefined [-Wsequence-point] D = A[m][B[m++]]; ^ Thus your testcase is invalid because of unsequenced modification and access to m. >From gcc-bugs-return-439940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 10 11:58:00 2014 Return-Path: <gcc-bugs-return-439940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 16718 invoked by alias); 10 Jan 2014 11:57:59 -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 16666 invoked by uid 48); 10 Jan 2014 11:57:55 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59743] [4.9 Regression] ICE: Segmentation fault Date: Fri, 10 Jan 2014 11:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: law at redhat dot com X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59743-4-snFuC6Dpbn@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59743-4@http.gcc.gnu.org/bugzilla/> References: <bug-59743-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-01/txt/msg01082.txt.bz2 Content-length: 464 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY743 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ah, there is: /* If the df_live problem is not defined, such as at -O0 and -O1, we still need to keep the luids up to date. This is normally done in the df_live problem since this problem has a forwards scan. */ if (!df_live) df_recompute_luids (bb); in df_lr_bb_local_compute, so I think luids are fine even at -O0/-O1.
next prev parent reply other threads:[~2014-01-10 11:40 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34678-4@http.gcc.gnu.org/bugzilla/> 2010-10-26 10:33 ` paolo.carlini at oracle dot com 2011-02-08 2:02 ` pinskia at gcc dot gnu.org 2011-04-01 19:22 ` pinskia at gcc dot gnu.org 2013-11-11 9:30 ` nmm1 at cam dot ac.uk 2013-11-11 13:37 ` vincent-gcc at vinc17 dot net 2013-11-11 16:38 ` joseph at codesourcery dot com 2013-11-11 17:32 ` nmm1 at cam dot ac.uk 2014-01-10 11:40 ` vincent-gcc at vinc17 dot net [this message] 2014-01-14 14:58 ` vincent-gcc at vinc17 dot net 2014-01-14 15:13 ` nmm1 at cam dot ac.uk 2014-01-14 15:52 ` vincent-gcc at vinc17 dot net 2014-01-14 17:22 ` nmm1 at cam dot ac.uk 2014-01-14 23:16 ` vincent-gcc at vinc17 dot net 2014-02-16 10:03 ` jackie.rosen at hushmail dot com 2020-04-16 15:35 ` vincent-gcc at vinc17 dot net 2023-01-06 17:29 ` pinskia at gcc dot gnu.org 2023-01-06 17:31 ` pinskia at gcc dot gnu.org 2023-01-06 19:29 ` tkoenig at gcc dot gnu.org 2023-01-06 22:14 ` tkoenig at gcc dot gnu.org 2023-01-07 11:14 ` tkoenig at gcc dot gnu.org 2023-01-07 12:14 ` tkoenig at gcc dot gnu.org 2008-01-04 18:56 [Bug c/34678] New: Optimization generates incorrect code with -frounding-math option merkert at comcast dot net 2008-01-05 12:08 ` [Bug middle-end/34678] Optimization generates incorrect code with -frounding-math option (#pragma STDC FENV_ACCESS not implemented) rguenth at gcc dot gnu dot org 2008-01-05 16:48 ` merkert at comcast dot net 2008-01-05 21:00 ` joseph at codesourcery dot com 2008-01-05 21:29 ` rguenth at gcc dot gnu dot org 2008-01-06 16:21 ` joseph at codesourcery dot com 2008-01-06 17:19 ` rguenth at gcc dot gnu dot org 2008-01-06 18:03 ` joseph at codesourcery dot com 2008-10-15 15:44 ` rguenth at gcc dot gnu dot org 2008-10-15 21:31 ` vincent at vinc17 dot org 2008-10-15 22:15 ` rguenth at gcc dot gnu dot org 2008-10-15 22:35 ` vincent at vinc17 dot org 2008-10-16 9:46 ` rguenth at gcc dot gnu dot org 2008-10-16 11:58 ` merkert at comcast dot net 2008-10-16 14:21 ` vincent at vinc17 dot org 2008-10-16 16:40 ` joseph at codesourcery dot com 2008-10-16 17:41 ` vincent at vinc17 dot 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-34678-4-vD4gdl4y2G@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).