public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96369] [8/9/10/11 Regression] Wrong evaluation order of || operator
Date: Fri, 31 Jul 2020 00:21:55 +0000 [thread overview]
Message-ID: <bug-96369-4-YRunP3Bgbo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96369-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96369
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |tree-optimization
Summary|Wrong evaluation order of |[8/9/10/11 Regression]
||| operator |Wrong evaluation order of
| ||| operator
--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Actually it appears the wrong code is being introduced somewhere in
fold_range_test (I didn't trace it further than that); the only front-end
involvement is that the front end does folding as part of conversions at
various points.
Testing with old compilers suggests this appeared between 4.8.1 and 4.8.3
(quite possibly through some backported change perturbing the exact sequence of
calls to folding functions rather than the actual underlying cause being
introduced in whatever backport).
next prev parent reply other threads:[~2020-07-31 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 14:14 [Bug c/96369] New: " frank_yzg at outlook dot com
2020-07-29 15:41 ` [Bug tree-optimization/96369] " glisse at gcc dot gnu.org
2020-07-30 5:57 ` [Bug c/96369] " rguenth at gcc dot gnu.org
2020-07-31 0:21 ` jsm28 at gcc dot gnu.org [this message]
2020-07-31 6:39 ` [Bug tree-optimization/96369] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-07-31 10:12 ` cvs-commit at gcc dot gnu.org
2020-07-31 10:12 ` [Bug tree-optimization/96369] [8/9/10 " rguenth at gcc dot gnu.org
2020-07-31 10:12 ` rguenth at gcc dot gnu.org
2020-09-11 12:11 ` cvs-commit at gcc dot gnu.org
2020-12-02 13:23 ` [Bug tree-optimization/96369] [8/9 " cvs-commit at gcc dot gnu.org
2021-03-17 11:14 ` [Bug tree-optimization/96369] [8 " cvs-commit at gcc dot gnu.org
2021-03-17 11:15 ` rguenth 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-96369-4-YRunP3Bgbo@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).