public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107404] [12/13 Regression] Wrong code with -O3 since r12-6416-g037cc0b4a6646cc8 Date: Wed, 26 Oct 2022 06:36:18 +0000 [thread overview] Message-ID: <bug-107404-4-GWRgWwHI1O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107404-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107404 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org Keywords|needs-bisection | Summary|[12/13 Regression] Wrong |[12/13 Regression] Wrong |code with -O3 |code with -O3 since | |r12-6416-g037cc0b4a6646cc8 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Started with r12-6416-g037cc0b4a6646cc8.
next prev parent reply other threads:[~2022-10-26 6:36 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 0:40 [Bug tree-optimization/107404] New: [12/13 Regression] Wrong code with -O3 vsevolod.livinskiy at gmail dot com 2022-10-26 0:59 ` [Bug tree-optimization/107404] " pinskia at gcc dot gnu.org 2022-10-26 1:07 ` pinskia at gcc dot gnu.org 2022-10-26 6:36 ` marxin at gcc dot gnu.org [this message] 2022-10-26 6:36 ` [Bug tree-optimization/107404] [12/13 Regression] Wrong code with -O3 since r12-6416-g037cc0b4a6646cc8 marxin at gcc dot gnu.org 2022-10-26 8:58 ` rsandifo at gcc dot gnu.org 2022-10-26 9:05 ` jakub at gcc dot gnu.org 2022-10-26 11:13 ` rsandifo at gcc dot gnu.org 2022-11-03 9:29 ` [Bug target/107404] " ubizjak at gmail dot com 2022-11-03 10:00 ` ubizjak at gmail dot com 2022-11-03 13:18 ` cvs-commit at gcc dot gnu.org 2022-11-03 16:13 ` cvs-commit at gcc dot gnu.org 2022-11-03 16:18 ` ubizjak at gmail 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-107404-4-GWRgWwHI1O@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).