public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan 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 20:09:02 +0000 [thread overview] Message-ID: <bug-94591-4-8wimPy933W@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 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acoplan at gcc dot gnu.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Alex Coplan <acoplan at gcc dot gnu.org> --- This is now fixed on master, although the fix will need backporting.
next prev parent reply other threads:[~2020-05-19 20:09 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 ` [Bug target/94591] [8/9/10/11 Regression] Assembler messages: Error: operand mismatch -- `rev64 v0.2d,v0.2d' (or `rev32 v0.2s,v0.2s') cvs-commit at gcc dot gnu.org 2020-05-19 20:09 ` acoplan at gcc dot gnu.org [this message] 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-8wimPy933W@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).