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 tree-optimization/113552] [11/12/13 Regression] vectorizer generates calls to vector math routines with 1 simd lane. Date: Mon, 15 Apr 2024 11:38:35 +0000 [thread overview] Message-ID: <bug-113552-4-swRbvfKxlx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113552-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113552 --- Comment #14 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:0c2fcf3ddfe93d1f403962c4bacbb5d55ab7d19d commit r11-11323-g0c2fcf3ddfe93d1f403962c4bacbb5d55ab7d19d Author: Tamar Christina <tamar.christina@arm.com> Date: Mon Apr 15 12:32:24 2024 +0100 [AArch64]: Do not allow SIMD clones with simdlen 1 [PR113552] This is a backport of g:306713c953d509720dc394c43c0890548bb0ae07. The AArch64 vector PCS does not allow simd calls with simdlen 1, however due to a bug we currently do allow it for num == 0. This causes us to emit a symbol that doesn't exist and we fail to link. gcc/ChangeLog: PR tree-optimization/113552 * config/aarch64/aarch64.c (aarch64_simd_clone_compute_vecsize_and_simdlen): Block simdlen 1. gcc/testsuite/ChangeLog: PR tree-optimization/113552 * gcc.target/aarch64/pr113552.c: New test. * gcc.target/aarch64/simd_pcs_attribute-3.c: Remove bogus check.
next prev parent reply other threads:[~2024-04-15 11:38 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-23 7:53 [Bug middle-end/113552] New: [11/12/13/14 " tnfchris at gcc dot gnu.org 2024-01-23 7:53 ` [Bug tree-optimization/113552] " tnfchris at gcc dot gnu.org 2024-01-23 8:13 ` rguenth at gcc dot gnu.org 2024-01-23 8:51 ` nsz at gcc dot gnu.org 2024-01-23 8:51 ` tnfchris at gcc dot gnu.org 2024-01-23 8:54 ` tnfchris at gcc dot gnu.org 2024-01-23 10:12 ` tnfchris at gcc dot gnu.org 2024-01-23 10:39 ` rguenth at gcc dot gnu.org 2024-01-23 10:56 ` rguenth at gcc dot gnu.org 2024-01-23 10:59 ` rguenth at gcc dot gnu.org 2024-01-23 11:19 ` tnfchris at gcc dot gnu.org 2024-01-23 11:57 ` rguenth at gcc dot gnu.org 2024-01-23 13:10 ` cvs-commit at gcc dot gnu.org 2024-01-24 15:58 ` cvs-commit at gcc dot gnu.org 2024-04-15 11:14 ` [Bug tree-optimization/113552] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-04-15 11:38 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-15 11:40 ` tnfchris 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-113552-4-swRbvfKxlx@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).