You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR-URL: #50629Fixes: #50561Fixes: #45091
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
A typical build invocation on x86 looks like this:
82
89
83
90
```sh
@@ -93,6 +100,15 @@ Example:
93
100
AVX2_CFLAGS=-mavx2 make
94
101
```
95
102
103
+
### AVX512
104
+
105
+
To build and include the AVX512 codec, set the `AVX512_CFLAGS` environment variable to a value that will turn on AVX512 support in your compiler, typically `-mavx512vl -mavx512vbmi`.
106
+
Example:
107
+
108
+
```sh
109
+
AVX512_CFLAGS="-mavx512vl -mavx512vbmi" make
110
+
```
111
+
96
112
The codec will only be used if runtime feature detection shows that the target machine supports AVX2.
97
113
98
114
### SSSE3
@@ -208,6 +224,7 @@ Mainly there for testing purposes, this is also useful on ARM where the only way
0 commit comments