public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112787] Codegen regression of large GCC vector extensions when enabling SVE Date: Mon, 19 Feb 2024 16:46:49 +0000 [thread overview] Message-ID: <bug-112787-4-ndGthGmrl2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112787-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112787 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Andre Simoes Dias Vieira <avieira@gcc.gnu.org>: https://gcc.gnu.org/g:e84c06f801fbf8376fe43719675a409f588f68bd commit r12-10165-ge84c06f801fbf8376fe43719675a409f588f68bd Author: Andre Vieira <andre.simoesdiasvieira@arm.com> Date: Wed Dec 20 16:41:52 2023 +0000 veclower: improve selection of vector mode when lowering [PR 112787] This patch addresses the issue reported in PR target/112787 by improving the compute type selection. We do this by not considering types with more elements than the type we are lowering since we'd reject such types anyway. gcc/ChangeLog: PR target/112787 * tree-vect-generic.cc (type_for_widest_vector_mode): Change function to use original vector type and check widest vector mode has at most the same number of elements. (get_compute_type): Pass original vector type rather than the element type to type_for_widest_vector_mode and remove now obsolete check for the number of elements. gcc/testsuite/ChangeLog: * gcc.target/aarch64/pr112787.c: New test. (cherry picked from commit a3ff76278efe006dc0b50249c8e5baf565bff56b)
next prev parent reply other threads:[~2024-02-19 16:46 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 17:31 [Bug target/112787] New: " avieira at gcc dot gnu.org 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 [this message] 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-ndGthGmrl2@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).