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/92342] [10/11/12 Regression] a small missed transformation into x?b:0 Date: Fri, 10 Mar 2023 19:25:57 +0000 [thread overview] Message-ID: <bug-92342-4-NoUFy1HqyV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Target Milestone|10.5 |13.0 Resolution|--- |FIXED --- Comment #31 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed in GCC 13. I don't mind this not being fixed on other branches.
prev parent reply other threads:[~2023-03-10 19:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92342-4@http.gcc.gnu.org/bugzilla/> 2020-05-07 11:56 ` [Bug rtl-optimization/92342] [10/11 " jakub at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-14 0:54 ` pinskia at gcc dot gnu.org 2021-11-22 0:57 ` [Bug tree-optimization/92342] [10/11/12 " pinskia at gcc dot gnu.org 2021-11-22 1:59 ` pinskia at gcc dot gnu.org 2021-11-22 4:13 ` pinskia at gcc dot gnu.org 2021-11-22 6:26 ` pinskia at gcc dot gnu.org 2022-06-28 10:38 ` [Bug tree-optimization/92342] [10/11/12/13 " jakub at gcc dot gnu.org 2023-01-07 9:38 ` roger at nextmovesoftware dot com 2023-01-12 21:49 ` cvs-commit at gcc dot gnu.org 2023-01-14 18:55 ` gabravier at gmail dot com 2023-01-15 19:11 ` [Bug tree-optimization/92342] [10/11/12 " roger at nextmovesoftware dot com 2023-03-10 19:25 ` pinskia at gcc dot gnu.org [this message]
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-92342-4-NoUFy1HqyV@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).