PING^1
On 8/13/21 15:41, H.J. Lu wrote:
On Fri, Aug 13, 2021 at 1:10 AM Martin Liška <mli...@suse.cz> wrote:
On 8/12/21 7:35 PM, H.J. Lu wrote:
What happens for arch=x86-64-v5?
pr101696.c:5:55: error: bad value (‘x86-64-v5’) for ‘target("arch=")’ attribute
5 | __attribute__ ((target ("arch=x86-64-v5"))) void foo () { __builtin_printf
("arch=x86-64-v4\n"); }
| ^
pr101696.c:5:55: note: valid arguments to ‘target("arch=")’ attribute are:
nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell
core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake
icelake-server cascadelake tigerlake cooperlake sapphirerapids alderlake bonnell atom
silvermont slm goldmont goldmont-plus tremont knl knm x86-64 x86-64-v2 x86-64-v3
x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3
opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2
bdver3 bdver4 znver1 znver2 znver3 btver1 btver2 native; did you mean ‘x86-64-v2’?
Which seems to me a reasonable error message.
The patch looks good to me.
Thanks.
