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/111542] [11/12/13/14 Regression] (a==0)&(b==0) into `(a|b) == 0` optimization sometimes gets in the way of other optimizations Date: Fri, 22 Sep 2023 18:55:36 +0000 [thread overview] Message-ID: <bug-111542-4-NV6xPrl7V1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111542-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111542 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |14.0 Summary|[11/12/13/14 Regression] |[11/12/13/14 Regression] | |(a==0)&(b==0) into `(a|b) | |== 0` optimization | |sometimes gets in the way | |of other optimizations Known to fail| |7.1.0 Known to work| |6.1.0
next prev parent reply other threads:[~2023-09-22 18:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-22 18:51 [Bug tree-optimization/111542] New: [11/12/13/14 Regression] pinskia at gcc dot gnu.org 2023-09-22 18:54 ` [Bug tree-optimization/111542] " pinskia at gcc dot gnu.org 2023-09-22 18:55 ` pinskia at gcc dot gnu.org [this message] 2023-09-23 20:14 ` [Bug tree-optimization/111542] [11/12/13/14 Regression] (a==0)&(b==0) into `(a|b) == 0` optimization sometimes gets in the way of other optimizations pinskia at gcc dot gnu.org 2023-09-23 20:23 ` pinskia at gcc dot gnu.org 2023-10-17 13:00 ` rguenth at gcc dot gnu.org 2024-05-07 7:42 ` [Bug tree-optimization/111542] [11/12/13/14/15 " 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-111542-4-NV6xPrl7V1@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).