public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105740] missed optimization switch transformation for conditions with duplicate conditions Date: Mon, 30 May 2022 09:57:42 +0000 [thread overview] Message-ID: <bug-105740-4-xFcgttkTwk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105740-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105740 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2022-05-30 Status|UNCONFIRMED |NEW CC| |marxin at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Yes, I can confirm that at time of if-to-switch conversion pass, the condition 'len > 3' is not extracted and is present in every condition.
next prev parent reply other threads:[~2022-05-30 9:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-26 11:26 [Bug tree-optimization/105740] New: " b.buschinski at googlemail dot com 2022-05-30 9:57 ` marxin at gcc dot gnu.org [this message] 2022-06-21 2:45 ` [Bug tree-optimization/105740] " luoxhu at gcc dot gnu.org 2022-06-21 7:30 ` marxin at gcc dot gnu.org 2022-06-21 9:02 ` rguenth at gcc dot gnu.org 2022-06-21 9:12 ` jakub at gcc dot gnu.org 2022-06-21 9:26 ` rguenther at suse dot de 2022-06-21 9:29 ` cvs-commit at gcc dot gnu.org 2022-06-22 6:19 ` luoxhu at gcc dot gnu.org 2022-06-27 13:58 ` marxin at gcc dot gnu.org 2022-07-01 2:06 ` luoxhu at gcc dot gnu.org 2022-07-08 10:46 ` marxin at gcc dot gnu.org 2023-06-26 6:43 ` b.buschinski at googlemail dot com
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-105740-4-xFcgttkTwk@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).