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/111734] [14 Regression] wrong code with '-O3 -fno-inline-functions-called-once -fno-inline-small-functions -fno-omit-frame-pointer -fno-toplevel-reorder -fno-tree-fre'
Date: Tue, 17 Oct 2023 13:11:50 +0000 [thread overview]
Message-ID: <bug-111734-4-gz51inLXCw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111734-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111734
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |jamborm at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Priority|P3 |P1
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
-fno-ipa-modref fixes it.
Fails with -O3 -fno-inline -fno-toplevel-reorder -fno-tree-fre
--- a-t.c.146t.pre 2023-10-17 15:07:52.544953598 +0200
+++ a-t.c.146t.pre.bad 2023-10-17 15:07:45.788953643 +0200
@@ -25,7 +25,6 @@
int _4;
<bb 2> [local count: 1073741824]:
- i = &e;
g.constprop (&i);
i.2_3 = i;
_4 = *i.2_3;
I think this is a duplicate of the modref / IPA-CP issue (failing to remember
the PR number) which IIRC has a patch under review.
next prev parent reply other threads:[~2023-10-17 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 10:02 [Bug c/111734] New: " 19373742 at buaa dot edu.cn
2023-10-09 10:03 ` [Bug c/111734] " 19373742 at buaa dot edu.cn
2023-10-09 12:42 ` 19373742 at buaa dot edu.cn
2023-10-10 2:38 ` [Bug tree-optimization/111734] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-17 13:11 ` rguenth at gcc dot gnu.org [this message]
2023-10-31 3:27 ` sjames at gcc dot gnu.org
2023-10-31 5:19 ` sjames at gcc dot gnu.org
2023-10-31 6:27 ` [Bug tree-optimization/111734] [14 Regression] wrong code with '-O3 -fno-inline-functions-called-once -fno-inline-small-functions -fno-omit-frame-pointer -fno-toplevel-reorder -fno-tree-fre' since r14-3226-gd073e2d75d9ed4 sjames at gcc dot gnu.org
2023-10-31 7:43 ` 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-111734-4-gz51inLXCw@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).