public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-9503] i386: Fix *aes<aeswideklvariant>u8 Date: Mon, 24 Jan 2022 09:21:33 +0000 (GMT) [thread overview] Message-ID: <20220124092133.77F903858417@sourceware.org> (raw) https://gcc.gnu.org/g:8e4c410bb0203405ce092b42f25f572dfff9fd78 commit r11-9503-g8e4c410bb0203405ce092b42f25f572dfff9fd78 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Jan 19 09:17:54 2022 +0100 i386: Fix *aes<aeswideklvariant>u8 grep '{[^|}]*}"' *.md found another spot, though dunno if we have sufficient effective targets etc. to add an -masm=intel test for it (and my installed binutils doesn't support it anyway). Binutils trunk testsuite shows the argument isn't omitted even in the Intel syntax: grep aesencwide *.s keylocker.s: aesencwide128kl 126(%edx) keylocker.s: aesencwide256kl 126(%edx) keylocker.s: aesencwide128kl [edx+126] keylocker.s: aesencwide256kl [edx+126] property-10.s: aesencwide128kl (%eax) x86-64-keylocker.s: aesencwide128kl 126(%rdx) x86-64-keylocker.s: aesencwide256kl 126(%rdx) x86-64-keylocker.s: aesencwide128kl [rdx+126] x86-64-keylocker.s: aesencwide256kl [rdx+126] and doesn't use any WHATEVER PTR. 2022-01-19 Jakub Jelinek <jakub@redhat.com> * config/i386/sse.md (*aes<aeswideklvariant>u*): Use %0 instead of {%0}. (cherry picked from commit 29a6db635f5eb38ba34d15a6ee35b00e753740e4) Diff: --- gcc/config/i386/sse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/i386/sse.md b/gcc/config/i386/sse.md index 25678c8145d..d31e10184c3 100644 --- a/gcc/config/i386/sse.md +++ b/gcc/config/i386/sse.md @@ -24281,5 +24281,5 @@ [(match_operand:BLK 0 "memory_operand" "m")] AESDECENCWIDEKL))])] "TARGET_WIDEKL" - "aes<aeswideklvariant>\t{%0}" + "aes<aeswideklvariant>\t%0" [(set_attr "type" "other")])
reply other threads:[~2022-01-24 9:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220124092133.77F903858417@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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).