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/94591] [8/9/10/11 Regression] Assembler messages: Error: operand mismatch -- `rev64 v0.2d,v0.2d' (or `rev32 v0.2s,v0.2s') Date: Tue, 19 May 2020 19:44:54 +0000 [thread overview] Message-ID: <bug-94591-4-Lg26QXdGcB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94591-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94591 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alex Coplan <acoplan@gcc.gnu.org>: https://gcc.gnu.org/g:98452668d362bb9e6358f7eb5cff69f4f5ab1d45 commit r11-502-g98452668d362bb9e6358f7eb5cff69f4f5ab1d45 Author: Alex Coplan <alex.coplan@arm.com> Date: Tue May 19 20:33:20 2020 +0100 [aarch64] PR target/94591: Don't generate invalid REV64 insns This fixes PR94591. The problem was the function aarch64_evpc_rev_local() matching vector permutations that were not reversals. In particular, prior to this patch, this function matched the identity permutation which led to generating bogus REV64 insns which were rejected by the assembler. gcc/ PR target/94591 * config/aarch64/aarch64.c (aarch64_evpc_rev_local): Don't match identity permutation. gcc/testsuite/ PR target/94591 * gcc.c-torture/execute/pr94591.c: New test.
next prev parent reply other threads:[~2020-05-19 19:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-14 10:26 [Bug target/94591] New: [8/9/10 Regression] Assembler messages: Error: operand mismatch -- `rev64 v0.2d,v0.2d' zsojka at seznam dot cz 2020-04-14 10:46 ` [Bug target/94591] " ktkachov at gcc dot gnu.org 2020-04-14 10:49 ` rguenth at gcc dot gnu.org 2020-04-29 10:06 ` zsojka at seznam dot cz 2020-05-19 19:44 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-19 20:09 ` [Bug target/94591] [8/9/10/11 Regression] Assembler messages: Error: operand mismatch -- `rev64 v0.2d,v0.2d' (or `rev32 v0.2s,v0.2s') acoplan at gcc dot gnu.org 2020-05-20 8:43 ` acoplan at gcc dot gnu.org 2020-05-29 13:06 ` cvs-commit at gcc dot gnu.org 2020-05-29 13:20 ` cvs-commit at gcc dot gnu.org 2020-05-29 13:23 ` cvs-commit at gcc dot gnu.org 2020-05-29 13:34 ` acoplan 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-94591-4-Lg26QXdGcB@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).