public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112787] New: Codegen regression of large GCC vector extensions when enabling SVE Date: Thu, 30 Nov 2023 17:31:27 +0000 [thread overview] Message-ID: <bug-112787-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112787 Bug ID: 112787 Summary: Codegen regression of large GCC vector extensions when enabling SVE Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: avieira at gcc dot gnu.org Target Milestone: --- When compiling: typedef int __attribute__((__vector_size__ (64))) vec; vec fn (vec a, vec b) { return a + b; } with '-O2 -march=armv8-a' vs '-O2 -march=armv8-a+sve' the codegen defaults to scalar rather than using Advanced SIMD vectors.
next reply other threads:[~2023-11-30 17:31 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 17:31 avieira at gcc dot gnu.org [this message] 2023-11-30 17:34 ` [Bug target/112787] " avieira at gcc dot gnu.org 2023-12-01 7:22 ` rguenth at gcc dot gnu.org 2023-12-20 16:44 ` cvs-commit at gcc dot gnu.org 2024-01-06 6:15 ` pinskia at gcc dot gnu.org 2024-02-19 16:15 ` cvs-commit at gcc dot gnu.org 2024-02-19 16:46 ` cvs-commit at gcc dot gnu.org 2024-03-18 22:46 ` ebotcazou at gcc dot gnu.org 2024-03-18 23:06 ` pinskia at gcc dot gnu.org 2024-03-18 23:11 ` pinskia at gcc dot gnu.org 2024-03-19 17:13 ` avieira at gcc dot gnu.org 2024-03-19 17:15 ` pinskia at gcc dot gnu.org 2024-03-19 17:25 ` avieira at gcc dot gnu.org 2024-03-26 15:07 ` avieira at gcc dot gnu.org 2024-03-27 9:20 ` ebotcazou at gcc dot gnu.org 2024-03-27 18:53 ` pinskia 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-112787-4@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).