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/108847] [11/12/13/14 Regression] unnecessary bitwise AND on boolean types and shifting of the "sign" bit Date: Sun, 17 Sep 2023 01:49:23 +0000 [thread overview] Message-ID: <bug-108847-4-4KF0yih2rh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108847-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108847 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=52345 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Funny, the match pattern in comment #5 is similar to the one which I was working on for PR 52345 .
next prev parent reply other threads:[~2023-09-17 1:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-19 13:37 [Bug middle-end/108847] New: unnecessary bitwise AND on boolean types lh_mouse at 126 dot com 2023-02-20 18:43 ` [Bug middle-end/108847] " pinskia at gcc dot gnu.org 2023-05-20 1:14 ` [Bug middle-end/108847] unnecessary bitwise AND on boolean types and shifting of the "sign" bit pinskia at gcc dot gnu.org 2023-05-20 23:31 ` pinskia at gcc dot gnu.org 2023-05-20 23:34 ` [Bug middle-end/108847] [10/11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-20 23:34 ` pinskia at gcc dot gnu.org 2023-05-20 23:36 ` pinskia at gcc dot gnu.org 2023-05-27 6:50 ` pinskia at gcc dot gnu.org 2023-05-27 7:02 ` pinskia at gcc dot gnu.org 2023-09-17 1:49 ` pinskia at gcc dot gnu.org [this message] 2024-03-08 15:38 ` [Bug middle-end/108847] [11/12/13/14 " law at gcc dot gnu.org 2024-05-07 7:40 ` [Bug middle-end/108847] [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-108847-4-4KF0yih2rh@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).