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/112994] [Regression] Missed optimization for redundancy computation elimination because pattern is broken Date: Wed, 13 Dec 2023 06:15:56 +0000 [thread overview] Message-ID: <bug-112994-4-db5shkOzNL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112994-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112994 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Target Milestone|--- |12.4 Keywords| |missed-optimization Last reconfirmed| |2023-12-13 Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- It might be a regression but we are still missing a pattern for: int n,m; void test(int a, int b){ m=(a*4)/(a*2); }
next prev parent reply other threads:[~2023-12-13 6:15 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-13 5:46 [Bug tree-optimization/112994] New: " 652023330028 at smail dot nju.edu.cn 2023-12-13 6:15 ` pinskia at gcc dot gnu.org [this message] 2023-12-13 8:24 ` [Bug tree-optimization/112994] [12/13/14 Regression] " rguenth at gcc dot gnu.org 2023-12-13 14:26 ` jakub at gcc dot gnu.org 2023-12-13 15:13 ` jakub at gcc dot gnu.org 2023-12-13 16:02 ` jakub at gcc dot gnu.org 2023-12-13 18:15 ` jakub at gcc dot gnu.org 2023-12-13 18:16 ` jakub at gcc dot gnu.org 2023-12-14 10:58 ` cvs-commit at gcc dot gnu.org 2023-12-14 11:07 ` cvs-commit at gcc dot gnu.org 2023-12-15 12:40 ` jakub 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-112994-4-db5shkOzNL@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).