public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96573] [10 Regression] Regression in optimization on x86-64 with -O3 Date: Fri, 07 Jul 2023 09:03:16 +0000 [thread overview] Message-ID: <bug-96573-4-vYRu2zJsIH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96573-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96573 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Known to work| |11.0 Target Milestone|10.5 |11.0 Known to fail| |10.5.0 --- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed in GCC 11.
prev parent reply other threads:[~2023-07-07 9:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-11 17:45 [Bug c/96573] New: [Regression] Regression in optimization on x86-64 with -O3 from GCC 9 to 10 remi.andruccioli at gmail dot com 2020-08-11 18:22 ` [Bug tree-optimization/96573] [10/11 Regression] Regression in optimization on x86-64 with -O3 jakub at gcc dot gnu.org 2020-08-12 15:42 ` remi.andruccioli at gmail dot com 2020-08-25 8:44 ` rguenth at gcc dot gnu.org 2021-03-31 9:13 ` rguenth at gcc dot gnu.org 2021-04-01 8:52 ` cvs-commit at gcc dot gnu.org 2021-04-01 9:22 ` [Bug tree-optimization/96573] [10 " jakub at gcc dot gnu.org 2021-04-04 19:42 ` pinskia at gcc dot gnu.org 2021-04-06 10:46 ` cvs-commit at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 9:03 ` rguenth 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-96573-4-vYRu2zJsIH@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).