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/96298] [11 Regression] wrong code with -O -fno-tree-forwprop
Date: Thu, 23 Jul 2020 11:50:24 +0000 [thread overview]
Message-ID: <bug-96298-4-u9GsrAy3de@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64-unknown-linux-gnu |powerpc64-unknown-linux-gnu
| |, x86_64-*-*
Ever confirmed|0 |1
Last reconfirmed| |2020-07-23
Status|UNCONFIRMED |NEW
Target Milestone|--- |11.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
On ppc64le I for example see
<bb 2> [local count: 119292720]:
a.0_1 = a;
_13 = VIEW_CONVERT_EXPR<long unsigned int>(a.0_1);
_6 = ~_13;
_10 = _13 & 9187201950435737471;
_12 = _6 & 9259542123273814144;
_21 = _10 + 9187201950435737471;
_22 = _21 ^ _12;
_23 = VIEW_CONVERT_EXPR<vector(8) unsigned char>(_22);
_28 = 9259542123273814144 - _10;
_29 = _12 ^ _28;
_30 = VIEW_CONVERT_EXPR<vector(8) unsigned char>(_29);
_31 = VIEW_CONVERT_EXPR<long unsigned int>(_30);
_32 = VIEW_CONVERT_EXPR<long unsigned int>(_23);
_33 = _32 ^ _31;
_34 = VIEW_CONVERT_EXPR<vector(8) unsigned char>(_33);
x = _34;
likewise on x86_64 with -mno-sse where it fails as well.
next prev parent reply other threads:[~2020-07-23 11:50 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 ` rguenth at gcc dot gnu.org [this message]
2020-07-23 11:55 ` [Bug tree-optimization/96298] " 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
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-u9GsrAy3de@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).