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/108076] [10/11/12/13 Regression] GCC with -O3 produces code which fails to link Date: Mon, 12 Dec 2022 16:19:31 +0000 [thread overview] Message-ID: <bug-108076-4-NPYcf69prx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108076-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108076 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-12-12 Known to work| |9.1.0, 9.2.0, 9.4.0, 9.5.0 Status|UNCONFIRMED |NEW Target Milestone|--- |10.5 Ever confirmed|0 |1 Known to fail| |10.1.0 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed.
next prev parent reply other threads:[~2022-12-12 16:19 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-12 14:53 [Bug c/108076] New: " martid0311 at gmail dot com 2022-12-12 14:54 ` [Bug c/108076] " martid0311 at gmail dot com 2022-12-12 15:15 ` [Bug tree-optimization/108076] [10/11/12/13 Regression] " amonakov at gcc dot gnu.org 2022-12-12 16:19 ` pinskia at gcc dot gnu.org [this message] 2022-12-12 16:30 ` jakub at gcc dot gnu.org 2022-12-12 16:38 ` rguenth at gcc dot gnu.org 2022-12-13 10:41 ` cvs-commit at gcc dot gnu.org 2022-12-13 10:56 ` [Bug tree-optimization/108076] [10/11/12 " rguenth at gcc dot gnu.org 2023-01-24 14:27 ` cvs-commit at gcc dot gnu.org 2023-05-02 12:03 ` [Bug tree-optimization/108076] [10/11 " cvs-commit at gcc dot gnu.org 2023-07-07 10:06 ` [Bug tree-optimization/108076] [10 " 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-108076-4-NPYcf69prx@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).