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/107254] [11 Regression] Wrong vectorizer code (GCC 11 only, Fortran) Date: Thu, 13 Oct 2022 18:56:30 +0000 [thread overview] Message-ID: <bug-107254-4-JMNNiUpfhR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107254-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107254 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs-bisection | Status|UNCONFIRMED |NEW Last reconfirmed| |2022-10-13 Ever confirmed|0 |1 CC| |marxin at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Fixed with r12-2051-g7d810646d421f697 and started with r11-2453-gc89366b12ff4f362. @Richi: Can you please take a look?
next prev parent reply other threads:[~2022-10-13 18:56 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-13 16:28 [Bug tree-optimization/107254] New: " bartoldeman at users dot sourceforge.net 2022-10-13 16:31 ` [Bug tree-optimization/107254] [11 Regression] " pinskia at gcc dot gnu.org 2022-10-13 18:56 ` marxin at gcc dot gnu.org [this message] 2022-10-13 19:02 ` pinskia at gcc dot gnu.org 2022-10-14 6:34 ` rguenth at gcc dot gnu.org 2022-10-14 7:50 ` [Bug tree-optimization/107254] [11/12/13 " rguenth at gcc dot gnu.org 2022-10-14 8:31 ` [Bug tree-optimization/107254] [11/12/13 Regression] Wrong vectorizer code (Fortran) marxin at gcc dot gnu.org 2022-10-14 8:52 ` [Bug tree-optimization/107254] [11/12/13 Regression] Wrong vectorizer code (Fortran) since r11-1501-gda2b7c7f0a136b4d rguenth at gcc dot gnu.org 2022-10-14 8:52 ` rguenth at gcc dot gnu.org 2022-10-14 9:19 ` rguenth at gcc dot gnu.org 2022-10-14 10:00 ` cvs-commit at gcc dot gnu.org 2022-10-14 10:01 ` [Bug tree-optimization/107254] [11/12 " rguenth at gcc dot gnu.org 2022-10-17 12:23 ` bartoldeman at users dot sourceforge.net 2022-10-17 13:11 ` cvs-commit at gcc dot gnu.org 2023-01-24 15:22 ` [Bug tree-optimization/107254] [11 " cvs-commit at gcc dot gnu.org 2023-01-24 15:23 ` 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-107254-4-JMNNiUpfhR@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).