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/111764] [11/12/13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu Date: Tue, 10 Oct 2023 20:57:50 +0000 [thread overview] Message-ID: <bug-111764-4-vbJdAkwea8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111764-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111764 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2023-10-10 Target Milestone|--- |11.5 Summary|Wrong code at -O3 on |[11/12/13/14 Regression] |x86_64-linux-gnu since |Wrong code at -O3 on |r11-5965-g04bff1bbfc1 |x86_64-linux-gnu Ever confirmed|0 |1 Known to work| |10.5.0 Keywords| |needs-bisection Known to fail| |11.1.0, 12.1.0, 13.1.0 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note r11-5965-g04bff1bbfc1 just exposed the issue, you can reproduce the issue before that with `-fno-vector-cost-model` added and it worked with that option in GCC 9.5.0 but was broken in GCC 10.1.0. Confirmed.
next prev parent reply other threads:[~2023-10-10 20:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-10 20:54 [Bug tree-optimization/111764] New: Wrong code at -O3 on x86_64-linux-gnu since r11-5965-g04bff1bbfc1 shaohua.li at inf dot ethz.ch 2023-10-10 20:57 ` pinskia at gcc dot gnu.org [this message] 2023-10-10 21:00 ` [Bug tree-optimization/111764] [11/12/13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu pinskia at gcc dot gnu.org 2023-10-11 13:36 ` rguenth at gcc dot gnu.org 2023-10-11 13:47 ` rguenth at gcc dot gnu.org 2023-10-12 6:49 ` rguenth at gcc dot gnu.org 2023-10-12 7:12 ` rguenth at gcc dot gnu.org 2023-10-12 8:22 ` cvs-commit at gcc dot gnu.org 2023-10-12 8:22 ` [Bug tree-optimization/111764] [11/12/13 " rguenth at gcc dot gnu.org 2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org 2023-11-27 13:09 ` [Bug tree-optimization/111764] [11/12 " cvs-commit at gcc dot gnu.org 2023-12-15 12:18 ` [Bug tree-optimization/111764] [11 " cvs-commit at gcc dot gnu.org 2023-12-15 12:22 ` 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-111764-4-vbJdAkwea8@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).