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/105463] [11/12/13 Regression] MVE: Wrong code, incorrect alignment assumption Date: Fri, 13 May 2022 10:25:10 +0000 [thread overview] Message-ID: <bug-105463-4-hosTP3kGLl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105463-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105463 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>: https://gcc.gnu.org/g:6a116728e27c4da65d84483c0e75561a7479d4d5 commit r13-417-g6a116728e27c4da65d84483c0e75561a7479d4d5 Author: Richard Earnshaw <rearnsha@arm.com> Date: Wed May 11 13:08:40 2022 +0100 arm: correctly handle misaligned MEMs on MVE [PR105463] Vector operations in MVE must be aligned to the element size, so if we are asked for a misaligned move in a wider mode we must recast it to a form suitable for the known alignment (larger elements have better address offset ranges, so there is some advantage to using wider element sizes if possible). Whilst fixing this, also rework the predicates used for validating operands - the Neon predicates are not right for MVE. gcc/ChangeLog: PR target/105463 * config/arm/mve.md (*movmisalign<mode>_mve_store): Use mve_memory_operand. (*movmisalign<mode>_mve_load): Likewise. * config/arm/vec-common.md (movmisalign<mode>): Convert to generator form... (@movmisalign<mode>): ... thus. Use generic predicates and then rework operands if they are not valid. For MVE rework to a narrower element size if the alignment is not high enough.
next prev parent reply other threads:[~2022-05-13 10:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 9:52 [Bug target/105463] New: [12/13 " acoplan at gcc dot gnu.org 2022-05-03 11:31 ` [Bug target/105463] " rguenth at gcc dot gnu.org 2022-05-03 11:34 ` rguenth at gcc dot gnu.org 2022-05-03 13:29 ` acoplan at gcc dot gnu.org 2022-05-03 13:42 ` [Bug target/105463] [11/12/13 " rguenth at gcc dot gnu.org 2022-05-03 14:59 ` rearnsha at gcc dot gnu.org 2022-05-03 16:19 ` acoplan at gcc dot gnu.org 2022-05-13 10:25 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-13 10:31 ` [Bug target/105463] [11/12 " rearnsha at gcc dot gnu.org 2022-07-26 11:34 ` rguenth at gcc dot gnu.org 2022-09-02 10:16 ` cvs-commit at gcc dot gnu.org 2022-09-02 11:20 ` [Bug target/105463] [11 " cvs-commit at gcc dot gnu.org 2022-09-02 11:21 ` rearnsha 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-105463-4-hosTP3kGLl@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).