public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/105126] [9/10/11/12 Regression] Optimization regression gcc inserts not needed movsx when using switch statement Date: Wed, 20 Apr 2022 10:18:39 +0000 [thread overview] Message-ID: <bug-105126-4-tdItGxPvfZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105126-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105126 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Bet this is related to the unfortunately still not existent type demotion pass (that would need to be followed by some late type promotion pass before expansion or before vectorization on the for vectorization only copy of loops). Or we could just demote switches. We do some demotions right now solely in the FEs (get_narrower and the like), which is something that could handle this case, but that wouldn't handle the case where the promotion is only visible after some propagation etc., and needs actually analysis of all the case label values (case labels out of bounds need to be DCEd or if they are ranges, narrowed).
next prev parent reply other threads:[~2022-04-20 10:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-01 13:42 [Bug regression/105126] New: " andre.schackier at gmail dot com 2022-04-01 15:39 ` [Bug regression/105126] " marxin at gcc dot gnu.org 2022-04-04 7:11 ` [Bug middle-end/105126] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2022-04-20 10:18 ` jakub at gcc dot gnu.org [this message] 2022-05-27 9:47 ` [Bug middle-end/105126] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2022-11-28 18:21 ` pinskia at gcc dot gnu.org 2023-01-11 12:36 ` marxin at gcc dot gnu.org 2023-07-07 10:42 ` [Bug middle-end/105126] [11/12/13/14 " 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-105126-4-tdItGxPvfZ@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).