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/103278] [12 Regression] Recent change to cddce inhibits switch optimization
Date: Tue, 16 Nov 2021 23:29:17 +0000 [thread overview]
Message-ID: <bug-103278-4-WZX0bNFx8v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103278-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103278
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target Milestone|--- |12.0
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2021-11-16
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
>;; Canonical GIMPLE case clusters: 9-10 12-13 32 48
I suspect there is some cost issue going on here.
DCE is now able to combine empty bb's into one which causes iftoswitch to have
a cost fit.
next prev parent reply other threads:[~2021-11-16 23:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 17:16 [Bug tree-optimization/103278] New: " law at gcc dot gnu.org
2021-11-16 23:25 ` [Bug tree-optimization/103278] " pinskia at gcc dot gnu.org
2021-11-16 23:29 ` pinskia at gcc dot gnu.org [this message]
2021-11-17 14:48 ` law at gcc dot gnu.org
2021-11-18 7:36 ` rguenth at gcc dot gnu.org
2021-11-18 8:48 ` rguenth at gcc dot gnu.org
2021-11-18 9:02 ` cvs-commit at gcc dot gnu.org
2021-11-18 9:04 ` rguenth at gcc dot gnu.org
2021-11-23 3:31 ` law at gcc dot gnu.org
2021-11-23 8:23 ` rguenth at gcc dot gnu.org
2021-11-23 8:25 ` marxin at gcc dot gnu.org
2021-11-29 15:23 ` marxin at gcc dot gnu.org
2021-11-30 7:22 ` rguenther at suse dot de
2021-11-30 13:48 ` cvs-commit at gcc dot gnu.org
2021-11-30 13:48 ` marxin 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-103278-4-WZX0bNFx8v@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).