public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Jakub Jelinek" <jakub@redhat.com>
Cc: "Uros Bizjak" <ubizjak@gmail.com>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH: Enable Intel AES/CLMUL
Date: Fri, 04 Apr 2008 15:58:00 -0000	[thread overview]
Message-ID: <6dc9ffc80804040846w329a4a15t8ee4a28c188bbf3d@mail.gmail.com> (raw)
In-Reply-To: <20080404145040.GE30807@devserv.devel.redhat.com>

On Fri, Apr 4, 2008 at 7:50 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Apr 04, 2008 at 04:33:51PM +0200, Uros Bizjak wrote:
>  > This will work just fine even without SSE (although a warning about
>  > changed ABI will be issued). We can even add AES functionality to the
>  > library this way (hint, hint ;)
>  >
>  > And using intrinsic, the situation will be actually just reversed to
>  > the situation you described below.
>
>  This doesn't make sense.  The aes instructions use SSE2 registers,
>  so IMNSHO you really have to enable sse2 to be able to emit aes/pclmul
>  instructions.  So it makes perfect sense for -maes to enable -msse2.
>
>

That is what I prefer. You will need SSE2 when you use -maes. Otherwise,
you can't really do much with AES. I will check in the version which -maes
enables SSE2. We can change it later before 4.4 release.

Thanks.


H.J.

  reply	other threads:[~2008-04-04 15:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 18:53 Uros Bizjak
2008-04-03 22:00 ` H.J. Lu
2008-04-03 23:17   ` H.J. Lu
2008-04-04  6:35   ` Uros Bizjak
2008-04-04 12:53     ` H.J. Lu
2008-04-04 13:29       ` Uros Bizjak
2008-04-04 13:32         ` H.J. Lu
2008-04-04 13:56           ` Uros Bizjak
2008-04-04 14:08             ` Uros Bizjak
2008-04-04 14:51             ` H.J. Lu
2008-04-04 14:56               ` Uros Bizjak
2008-04-04 15:00                 ` Jakub Jelinek
2008-04-04 15:58                   ` H.J. Lu [this message]
2008-04-04 16:33                   ` Uros Bizjak
2008-04-04 15:31                 ` H.J. Lu
2008-04-04 16:08                   ` Uros Bizjak
2008-04-04 20:27           ` Michael Meissner
2008-04-04 20:43             ` H.J. Lu
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 14:31 H.J. Lu
2008-04-03 16:21 ` Daniel Berlin
2008-04-03 16:23   ` H.J. Lu

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=6dc9ffc80804040846w329a4a15t8ee4a28c188bbf3d@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=ubizjak@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).