From: "Uros Bizjak" <ubizjak@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH: Enable Intel AES/CLMUL
Date: Fri, 04 Apr 2008 13:56:00 -0000 [thread overview]
Message-ID: <5787cf470804040636ha78e8bcs215da56304201c19@mail.gmail.com> (raw)
In-Reply-To: <20080404132854.GA9234@lucon.org>
On Fri, Apr 4, 2008 at 3:28 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> > > SSE doesn't support V2DI. You need at least SSE2.
> > >
> >
> > OK.
> > This practically forces usage of -msse4.1 for -maes/-mclmul, since
> > these instructions are used only through intrinsics, defined in their
> > corresponding header file. wmmintrin.h includes smmintrin.h that will
> > error out by #ifndef __SSE4_1__.
> >
> > I think that user should explicitly enable sse4.1 manually in the
> > command line together with -maes/-mclmul to access these new
> > instructions. Including wmmintrin.h will error out when neither
> > -maes/-mclmul is enabled, and smmintrin.h will error out with a
> > message that SSE4.1 instruction set is not enabled.
>
> There is a proposal to get rid of all *mmintrin.h. Users should
> include one header file, something like <ia32intrin.h> ,for all
> current and future intrinsics. The name of the meta intrinsic
> heade file hasn't be decided. Do we have any preferences/suggestions?
>
> With that in mind, I will change it to include emmintrin.h.
OK. So, we require user to pass at least -msse2 in addition to
-maes/-mclmul then? The errors will be informative, so there will be
no confusion.
> > "instruction set" or "instructions" in the error message?
>
> I can use instructions.
This is up to your taste, "instruction set" just sound too fancy for
me for a pack of instructions ;)
Uros.
WARNING: multiple messages have this Message-ID
From: "Uros Bizjak" <ubizjak@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH: Enable Intel AES/CLMUL
Date: Fri, 04 Apr 2008 14:08:00 -0000 [thread overview]
Message-ID: <5787cf470804040636ha78e8bcs215da56304201c19@mail.gmail.com> (raw)
Message-ID: <20080404140800.izM9pybO00fAN36myt-ftrEz3riHE2z85gfZP6C4Ueo@z> (raw)
In-Reply-To: <20080404132854.GA9234@lucon.org>
On Fri, Apr 4, 2008 at 3:28 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> > > SSE doesn't support V2DI. You need at least SSE2.
> > >
> >
> > OK.
> > This practically forces usage of -msse4.1 for -maes/-mclmul, since
> > these instructions are used only through intrinsics, defined in their
> > corresponding header file. wmmintrin.h includes smmintrin.h that will
> > error out by #ifndef __SSE4_1__.
> >
> > I think that user should explicitly enable sse4.1 manually in the
> > command line together with -maes/-mclmul to access these new
> > instructions. Including wmmintrin.h will error out when neither
> > -maes/-mclmul is enabled, and smmintrin.h will error out with a
> > message that SSE4.1 instruction set is not enabled.
>
> There is a proposal to get rid of all *mmintrin.h. Users should
> include one header file, something like <ia32intrin.h> ,for all
> current and future intrinsics. The name of the meta intrinsic
> heade file hasn't be decided. Do we have any preferences/suggestions?
>
> With that in mind, I will change it to include emmintrin.h.
OK. So, we require user to pass at least -msse2 in addition to
-maes/-mclmul then? The errors will be informative, so there will be
no confusion.
> > "instruction set" or "instructions" in the error message?
>
> I can use instructions.
This is up to your taste, "instruction set" just sound too fancy for
me for a pack of instructions ;)
Uros.
next prev parent reply other threads:[~2008-04-04 13:38 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 [this message]
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
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=5787cf470804040636ha78e8bcs215da56304201c19@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@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).