Hi Paul,
I'd rather not move them into immintrin.h. The current situation is that if you
include emmintrin.h you get "too many" intrinsics w.r.t to the Intel docs (and
immintrin.h is just right, since it recursively includes emmintrin.h), while if
we move it to immintrin.h, including emmintrin.
Argh.
I'll revert, and figure out what to do with it later.
Sorry about the breakage.
Michael
-Original Message-
From: İsmail Dönmez [mailto:ism...@i10z.com]
Sent: Tuesday, August 25, 2015 14:17
To: Kuperstein, Michael M
Cc: cfe-commits@lists.llvm.org
Subject: Re: r245923 - [X86] Expose
I’m not sure how much people actually use these, but the AVX-512 versions of
these, at least, can be very useful internally to implement AVX-512 intrinsics.
For AVX-512, we use the same GCC builtin for all 3 versions of the intrinsic
(pass-through masked, set to zero masked, and unmasked). This i
