public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/91384] [9/10/11/12 Regression] Compare with negation is not eliminated Date: Mon, 28 Feb 2022 18:21:59 +0000 [thread overview] Message-ID: <bug-91384-4-kXKzGq5sMa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91384-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91384 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |roger at nextmovesoftware dot com Assignee|unassigned at gcc dot gnu.org |roger at nextmovesoftware dot com --- Comment #15 from Roger Sayle <roger at nextmovesoftware dot com> --- Patch proposed. https://gcc.gnu.org/pipermail/gcc-patches/2022-February/591013.html
next prev parent reply other threads:[~2022-02-28 18:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91384-4@http.gcc.gnu.org/bugzilla/> 2020-04-18 18:04 ` [Bug tree-optimization/91384] [8/9/10 " law at redhat dot com 2020-12-10 10:03 ` [Bug tree-optimization/91384] [8/9/10/11 " ubizjak at gmail dot com 2020-12-10 12:40 ` ubizjak at gmail dot com 2020-12-10 13:11 ` rguenth at gcc dot gnu.org 2020-12-10 13:17 ` rguenth at gcc dot gnu.org 2021-05-14 9:52 ` [Bug middle-end/91384] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:15 ` rguenth at gcc dot gnu.org 2021-12-22 16:05 ` [Bug tree-optimization/91384] " pinskia at gcc dot gnu.org 2021-12-22 16:07 ` pinskia at gcc dot gnu.org 2022-02-28 18:21 ` roger at nextmovesoftware dot com [this message] 2022-02-28 22:32 ` cvs-commit at gcc dot gnu.org 2022-03-02 12:07 ` roger at nextmovesoftware 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-91384-4-kXKzGq5sMa@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).