Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 18 Apr 2015 11:33:45 +0200
From: magnum <>
Subject: Re: Re: AVX512 support detection

On 2015-04-18 05:05, Lei Zhang wrote:
> On Apr 18, 2015, at 11:01 AM, Lei Zhang <> wrote:
>> As a brief reference, they're:
>> __AVX512BW__	- Byte and Word instructions
>> __AVX512CD__	- Conflict Detection instructions
>> __AVX512DQ__	- Doubleword and Quadword instructions
>> __AVX512ER__	- Exponential and Reciprocal instructions
>> __AVX512F__		- Foundation instructions
>> __AVX512PF__	- Prefetch instructions
>> __AVX512VL__	- Vector Length extensions
> For the full reference, see <>.

Some grep-fu

$ grep ^_mm512 /usr/local/include/(...)/avx512fintrin.h|awk '{print
$1}'|sort -u >512f.txt

$ grep -Eo '_mm512[^(]+' pseudo_intrinsics.h | sort -u >pseudo512.txt

Here's intrinsics we potentially use that are not present in 512F:

$ grep -wvf 512f.txt pseudo512.txt

Of those, I guess at least the following are not AVX512BW either:

vcvtsi32           (currently used for SSE4.1 <= arch < AVX2)
vmask2int          (currently used for AVX512/MIC, no pseudo)
vpermute2x128      (not used at all, we can drop it)
vpermute4x64_epi64 (not used at all, we can drop it)


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.