public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/96298] [11 Regression] wrong code with -O -fno-tree-forwprop
Date: Thu, 23 Jul 2020 17:49:55 +0000 [thread overview]
Message-ID: <bug-96298-4-XJrtwBDTeP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96298-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96298
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:
https://gcc.gnu.org/g:d4b3ea941b1a15cadb79e7ff8a36891131f8804b
commit r11-2296-gd4b3ea941b1a15cadb79e7ff8a36891131f8804b
Author: Roger Sayle <roger@nextmovesoftware.com>
Date: Thu Jul 23 18:48:54 2020 +0100
Resolve regression rtl-optimization/96298. Sorry for the breakage.
2020-07-23 Roger Sayle <roger@nextmovesoftware.com>
gcc/ChangeLog
PR rtl-optimization/96298
* simplify-rtx.c (simplify_binary_operation_1) [XOR]: Xor doesn't
distribute over xor, so (a^b)^(c^b) is not the same as (a^c)^b.
next prev parent reply other threads:[~2020-07-23 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 10:17 [Bug tree-optimization/96298] New: " zsojka at seznam dot cz
2020-07-23 11:50 ` [Bug tree-optimization/96298] " rguenth at gcc dot gnu.org
2020-07-23 11:55 ` rguenth at gcc dot gnu.org
2020-07-23 12:10 ` [Bug rtl-optimization/96298] " segher at gcc dot gnu.org
2020-07-23 12:13 ` marxin at gcc dot gnu.org
2020-07-23 12:56 ` segher at gcc dot gnu.org
2020-07-23 14:01 ` marxin at gcc dot gnu.org
2020-07-23 17:14 ` segher at gcc dot gnu.org
2020-07-23 17:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-18 13:46 ` cvs-commit at gcc dot gnu.org
2020-08-18 13:58 ` roger at nextmovesoftware dot com
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-96298-4-XJrtwBDTeP@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).