public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102892] [12 Regression] Dead Code Elimination Regression at -O3 (trunk vs 11.2.0)
Date: Wed, 10 Nov 2021 15:42:19 +0000 [thread overview]
Message-ID: <bug-102892-4-nEowAQ47rg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102892-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102892
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
There's no call to foo in current trunk.
It seems to be gone in the .ccp4 dump which runs after vrp2. This probably
went away with VRP2's switch to ranger.
Ideally we should add a testcase to the suite. Could someone take care of
this?
Anywhoo, fixed.
next prev parent reply other threads:[~2021-11-10 15:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 9:39 [Bug tree-optimization/102892] New: " theodort at inf dot ethz.ch
2021-10-22 9:48 ` [Bug tree-optimization/102892] " aldyh at gcc dot gnu.org
2021-10-22 21:19 ` pinskia at gcc dot gnu.org
2021-10-23 9:29 ` aldyh at gcc dot gnu.org
2021-11-10 14:24 ` marxin at gcc dot gnu.org
2021-11-10 15:42 ` aldyh at gcc dot gnu.org [this message]
2021-11-10 15:46 ` marxin at gcc dot gnu.org
2021-11-10 15:52 ` aldyh at gcc dot gnu.org
2021-11-10 19:27 ` cvs-commit at gcc dot gnu.org
2022-03-28 9:18 ` ebotcazou at gcc dot gnu.org
2022-03-28 14:37 ` aldyh at gcc dot gnu.org
2022-03-28 14:55 ` jakub at gcc dot gnu.org
2022-04-22 3:04 ` jiawei at iscas dot ac.cn
2022-05-04 0:50 ` [Bug tree-optimization/102892] [12/13 " palmer at gcc dot gnu.org
2022-05-04 0:50 ` palmer at gcc dot gnu.org
2022-05-04 11:58 ` jiawei at iscas dot ac.cn
2022-05-06 8:31 ` jakub at gcc dot gnu.org
2022-07-26 13:21 ` rguenth at gcc dot gnu.org
2022-09-29 22:34 ` cvs-commit at gcc dot gnu.org
2022-10-19 9:42 ` cvs-commit at gcc dot gnu.org
2022-10-19 9: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-102892-4-nEowAQ47rg@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).