This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: What is the builtin for _mm_sha256rnds2_epu32?
- From: Jeffrey Walton <noloader at gmail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Tue, 18 Apr 2017 07:15:44 -0400
- Subject: Re: What is the builtin for _mm_sha256rnds2_epu32?
- Authentication-results: sourceware.org; auth=none
- References: <CAH8yC8mFFzn_R-=jP89jNEgbByPRC8FFuxp+QUZVTp_EtU16QA@mail.gmail.com> <alpine.DEB.2.20.1704181030330.2343@stedding.saclay.inria.fr> <CAH8yC8=AJcjq4CrB9khsGgb2qatOKPqrCzxu0uvTxZiQ2N1pRg@mail.gmail.com> <CAH6eHdQutdpuCywK39kaAzzW06_+kB5KMCLUQA2PYAqVzGZA2w@mail.gmail.com> <CAH8yC8mXArV-Z9gvGyoM5Ndza5CFEMHBLhW-fG5J=uW=Dt6VWg@mail.gmail.com> <CAH6eHdT=9Ha_wM5fXJK-huj+C+EPvFsub4gkpvCiOPEux=fbJg@mail.gmail.com>
- Reply-to: noloader at gmail dot com
On Tue, Apr 18, 2017 at 5:39 AM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 18 April 2017 at 10:37, Jeffrey Walton wrote:
>> Intrinsics could have worked everywhere, but something else was provided.
>
> Because something else was requested.
Lets clear that up now. Here's the quote of what was requested:
</QUOTE>
Please make all headers for intrinsics be includable without special
compiler flags. [Example redacted].
Not only that, please make all the intrinsics functions be defined and
ready to be used. [Example redacted].
</QUOTE>
> If you want a different change,
> ask for it, don't complain it wasn't provided in response to a
> different request.
I wanted the same thing that was requested, but its a moot point now.
The earliest it would be usable in the mainstream is 5 or 7 years or
so. There's no guarantee it will be implemented, and no guarantee when
a distro will pick it up.
(The example showed freestanding functions that always returned a
constant value. I'd like to use it in member functions, and functions
that returned something other than a constant too.).
Jeff