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/109002] [13 Regression] -O1 -ftree-pre -ftree-partial-pre results in stall value
Date: Fri, 03 Mar 2023 09:55:36 +0000 [thread overview]
Message-ID: <bug-109002-4-ul2PFudbAi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109002-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109002
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|-O1 -ftree-pre |[13 Regression] -O1
|-ftree-partial-pre results |-ftree-pre
|in stall value |-ftree-partial-pre results
| |in stall value
Target Milestone|--- |13.0
Known to work| |12.2.0
Priority|P3 |P1
Keywords| |needs-bisection
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Looks like GCC 12 "works", I suspect the compile-time optimizations in pruning
to be the reason since PA_IN has bogus virtual operands in expressions which is
what the fix fixes.
next prev parent reply other threads:[~2023-03-03 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 6:40 [Bug tree-optimization/109002] New: " akihiko.odaki at daynix dot com
2023-03-03 6:51 ` [Bug tree-optimization/109002] " pinskia at gcc dot gnu.org
2023-03-03 6:58 ` akihiko.odaki at daynix dot com
2023-03-03 8:50 ` rguenth at gcc dot gnu.org
2023-03-03 9:38 ` rguenth at gcc dot gnu.org
2023-03-03 9:55 ` rguenth at gcc dot gnu.org [this message]
2023-03-03 11:07 ` [Bug tree-optimization/109002] [13 Regression] " cvs-commit at gcc dot gnu.org
2023-03-03 11:07 ` 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-109002-4-ul2PFudbAi@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).