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/107254] [11/12/13 Regression] Wrong vectorizer code (GCC 11 only, Fortran)
Date: Fri, 14 Oct 2022 07:50:15 +0000 [thread overview]
Message-ID: <bug-107254-4-CsSM8xmcoN@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[11 Regression] Wrong |[11/12/13 Regression] Wrong
|vectorizer code (GCC 11 |vectorizer code (GCC 11
|only, Fortran) |only, Fortran)
Priority|P3 |P2
Known to work|12.1.0 |
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, the testcase still fails with -O2 -ftree-vectorize -mavx2 -mno-fma
-fno-vect-cost-model on the GCC 12 branch and trunk but works with these flags
on the GCC 10 branch.
Interestingly it doesn't fail with -mprefer-vector-width=128 (which doesn't
require versioning for aliasing).
next prev parent reply other threads:[~2022-10-14 7:50 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
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 ` rguenth at gcc dot gnu.org [this message]
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-CsSM8xmcoN@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: link
Be 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).