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 middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0' Date: Tue, 18 Jul 2023 19:39:56 +0000 [thread overview] Message-ID: <bug-110726-4-zSMprFz17v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110726-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110726 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- /* a | (a == b) --> a | (b^1) (boolean version of the above). */ (simplify (bit_ior:c @0 (nop_convert? (eq:c @0 @1))) (bit_ior @0 (bit_xor @1 { build_one_cst (type); }))) So I guess the issue is eq on generic has an integer type rather than boolean type ...
next prev parent reply other threads:[~2023-07-18 19:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 19:09 [Bug middle-end/110726] New: " slyfox at gcc dot gnu.org 2023-07-18 19:29 ` [Bug middle-end/110726] " pinskia at gcc dot gnu.org 2023-07-18 19:29 ` pinskia at gcc dot gnu.org 2023-07-18 19:32 ` pinskia at gcc dot gnu.org 2023-07-18 19:36 ` pinskia at gcc dot gnu.org 2023-07-18 19:36 ` pinskia at gcc dot gnu.org 2023-07-18 19:39 ` pinskia at gcc dot gnu.org [this message] 2023-07-18 20:04 ` pinskia at gcc dot gnu.org 2023-07-18 20:31 ` pinskia at gcc dot gnu.org 2023-07-18 21:37 ` slyfox at gcc dot gnu.org 2023-07-18 21:42 ` pinskia at gcc dot gnu.org 2023-07-19 2:02 ` pinskia at gcc dot gnu.org 2023-07-19 6:13 ` slyfox at gcc dot gnu.org 2023-07-19 16:16 ` cvs-commit at gcc dot gnu.org 2023-07-19 16:17 ` pinskia 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-110726-4-zSMprFz17v@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).