public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111864] [12/13/14 Regression] Dead Code Elimination Regression Date: Wed, 18 Oct 2023 16:15:05 +0000 [thread overview] Message-ID: <bug-111864-4-FAkZS44Y73@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111864-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111864 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2023-10-18 Keywords| |needs-bisection Status|UNCONFIRMED |NEW Target Milestone|14.0 |12.4 Summary|[14 Regression] Dead Code |[12/13/14 Regression] Dead |Elimination Regression |Code Elimination Regression |since r14-4038-gb975c0dc3be | --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed but this is just happened to be a side effect. In forwprop1 we can change: ``` # iftmp.5_11 = PHI <1(3), 0(4)> _4 = iftmp.5_11 <= 0; _5 = (short int) _4; _25 = (int) _4; _26 = _25 << 5; _29 = (short int) _4; _27 = _29 << 5; _6 = (int) _27; if (_27 != 0) ``` Into just: ``` # iftmp.5_11 = PHI <1(3), 0(4)> if (iftmp.5_11 <= 0) ``` And then ethread is able to thread through that bb. You get the same missed optimization with removing the call to a. that is changing: ``` short v = a((g && p(t)) <= 0, 5); ``` to ``` short v = ((g && p(t)) <= 0); ``` Which then becomes a regression between GCC 11 and GCC 12.
next prev parent reply other threads:[~2023-10-18 16:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-18 14:10 [Bug tree-optimization/111864] New: [14 Regression] Dead Code Elimination Regression since r14-4038-gb975c0dc3be theodort at inf dot ethz.ch 2023-10-18 15:09 ` [Bug tree-optimization/111864] " pinskia at gcc dot gnu.org 2023-10-18 16:15 ` pinskia at gcc dot gnu.org [this message] 2024-03-07 21:04 ` [Bug tree-optimization/111864] [12/13/14 Regression] Dead Code Elimination Regression law at gcc dot gnu.org 2024-03-09 5:31 ` law at gcc dot gnu.org 2024-03-15 13:25 ` aldyh 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-111864-4-FAkZS44Y73@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: linkBe 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).