From: Uros Bizjak <ubizjak@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Kirill Yukhin <kirill.yukhin@gmail.com>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] x86: VAESDEC{,LAST} allow memory inputs
Date: Fri, 21 Dec 2018 09:07:00 -0000 [thread overview]
Message-ID: <CAFULd4ak818x_ac7vCCv21vdM_nevJvaiyseraEujZyxXkU3aA@mail.gmail.com> (raw)
In-Reply-To: <5C1CA7CD020000780020864C@prv1-mh.provo.novell.com>
On Fri, Dec 21, 2018 at 9:43 AM Jan Beulich <JBeulich@suse.com> wrote:
>
> They are no different from their VAESENC{,LAST} counterparts in this
> regard.
>
> gcc/
> 2018-12-21 Jan Beulich <jbeulich@suse.com>
>
> * config/i386/sse.md (vaesdec_<mode>, vaesdeclast_<mode>): Allow
> memory input.
OK.
Thanks,
Uros.
> --- a/gcc/config/i386/sse.md
> +++ b/gcc/config/i386/sse.md
> @@ -21659,7 +21659,7 @@
> [(set (match_operand:VI1_AVX512VL_F 0 "register_operand" "=v")
> (unspec:VI1_AVX512VL_F
> [(match_operand:VI1_AVX512VL_F 1 "register_operand" "v")
> - (match_operand:VI1_AVX512VL_F 2 "vector_operand" "v")]
> + (match_operand:VI1_AVX512VL_F 2 "vector_operand" "vm")]
> UNSPEC_VAESDEC))]
> "TARGET_VAES"
> "vaesdec\t{%2, %1, %0|%0, %1, %2}"
> @@ -21669,7 +21669,7 @@
> [(set (match_operand:VI1_AVX512VL_F 0 "register_operand" "=v")
> (unspec:VI1_AVX512VL_F
> [(match_operand:VI1_AVX512VL_F 1 "register_operand" "v")
> - (match_operand:VI1_AVX512VL_F 2 "vector_operand" "v")]
> + (match_operand:VI1_AVX512VL_F 2 "vector_operand" "vm")]
> UNSPEC_VAESDECLAST))]
> "TARGET_VAES"
> "vaesdeclast\t{%2, %1, %0|%0, %1, %2}"
>
>
>
prev parent reply other threads:[~2018-12-21 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:51 Jan Beulich
2018-12-21 9:07 ` Uros Bizjak [this message]
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=CAFULd4ak818x_ac7vCCv21vdM_nevJvaiyseraEujZyxXkU3aA@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=JBeulich@suse.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=kirill.yukhin@gmail.com \
/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: link
Be 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).