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/98119] [10 Regression] SVE: Wrong code with -O1 -ftree-vectorize -msve-vector-bits=512 -mtune=thunderx Date: Fri, 23 Apr 2021 16:17:24 +0000 [thread overview] Message-ID: <bug-98119-4-RKsp903kbP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98119-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98119 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:367aa5ee879c6bbfc4bf7ae94c680f0614581661 commit r10-9759-g367aa5ee879c6bbfc4bf7ae94c680f0614581661 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Fri Apr 23 17:17:11 2021 +0100 aarch64: Fix target alignment for SVE [PR98119] The vectoriser supports peeling for alignment using predication: we move back to the previous aligned boundary and make the skipped elements inactive in the first loop iteration. As it happens, the costs for existing CPUs give an equal cost to aligned and unaligned accesses, so this feature is rarely used. However, the PR shows that when the feature was forced on, we were still trying to align to a full-vector boundary even when using partial vectors. gcc/ PR target/98119 * config/aarch64/aarch64.c (aarch64_vectorize_preferred_vector_alignment): Query the size of the provided SVE vector; do not assume that all SVE vectors have the same size. gcc/testsuite/ PR target/98119 * gcc.target/aarch64/sve/pr98119.c: New test. (cherry picked from commit 1393938e4c7dab9306cdce5a73d93b242fc246ec)
next prev parent reply other threads:[~2021-04-23 16:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-03 12:20 [Bug target/98119] New: " acoplan at gcc dot gnu.org 2020-12-03 13:06 ` [Bug target/98119] " rsandifo at gcc dot gnu.org 2020-12-07 9:32 ` [Bug target/98119] [10/11 Regression] " acoplan at gcc dot gnu.org 2020-12-07 12:45 ` rguenth at gcc dot gnu.org 2021-01-14 11:00 ` rguenth at gcc dot gnu.org 2021-03-30 15:06 ` rsandifo at gcc dot gnu.org 2021-03-31 10:26 ` cvs-commit at gcc dot gnu.org 2021-03-31 20:39 ` [Bug target/98119] [10 " rsandifo at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-23 16:17 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-23 16:19 ` rsandifo 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-98119-4-RKsp903kbP@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).