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/114324] [13/14 Regression] AVX2 vectorisation performance regression with gfortran 13/14 Date: Wed, 13 Mar 2024 19:45:11 +0000 [thread overview] Message-ID: <bug-114324-4-mhvhkFjqn4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114324-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114324 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target Milestone|--- |12.4 Last reconfirmed| |2024-03-13 Status|UNCONFIRMED |NEW Summary|AVX2 vectorisation |[13/14 Regression] AVX2 |performance regression with |vectorisation performance |gfortran 13/14 |regression with gfortran | |13/14 Blocks| |53947 Component|target |tree-optimization --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Definitely there is some vectorization changes happening. Confirmed. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations
next prev parent reply other threads:[~2024-03-13 19:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-13 12:52 [Bug fortran/114324] New: " mjr19 at cam dot ac.uk 2024-03-13 19:45 ` pinskia at gcc dot gnu.org [this message] 2024-03-14 8:32 ` [Bug tree-optimization/114324] [13/14 Regression] " rguenth at gcc dot gnu.org 2024-03-14 8:32 ` rguenth at gcc dot gnu.org 2024-03-14 10:37 ` rguenth at gcc dot gnu.org 2024-03-15 20:06 ` mjr19 at cam dot ac.uk 2024-05-01 13:21 ` [Bug tree-optimization/114324] [13/14/15 " mjr19 at cam dot ac.uk 2024-05-21 9:19 ` jakub 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-114324-4-mhvhkFjqn4@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).