public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96369] [8/9/10 Regression] Wrong evaluation order of || operator Date: Fri, 31 Jul 2020 10:12:44 +0000 [thread overview] Message-ID: <bug-96369-4-xntfeOFVmd@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.0 Summary|[8/9/10/11 Regression] |[8/9/10 Regression] Wrong |Wrong evaluation order of |evaluation order of || ||| operator |operator Known to fail|11.0 |10.2.0 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed on trunk sofar.
next prev parent reply other threads:[~2020-07-31 10:12 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 ` [Bug tree-optimization/96369] [8/9/10/11 Regression] " jsm28 at gcc dot gnu.org 2020-07-31 6:39 ` rguenth at gcc dot gnu.org 2020-07-31 10:12 ` cvs-commit at gcc dot gnu.org 2020-07-31 10:12 ` rguenth at gcc dot gnu.org [this message] 2020-07-31 10:12 ` [Bug tree-optimization/96369] [8/9/10 " 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-xntfeOFVmd@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).