https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105640
--- Comment #1 from Jakub Jelinek ---
It isn't implemented on anything but x86, nvptx and gcn.
https://gcc.gnu.org/legacy-ml/gcc-patches/2019-10/threads.html#02066
has some more details.
aarch64 would be another HPC related target.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105640
--- Comment #2 from Jakub Jelinek ---
And no, t-omp-device isn't needed, that one is solely for targets that can be
used for offloading. i386 has it because of the intelmic offloading.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105640
--- Comment #3 from Jakub Jelinek ---
I'll also cite my response in
https://mailman.openmp.org/mailman/private/omp-lang/2020/016879.html
"The rationale for not using sm_XX for arch is that at least users of
compilers that target more than one C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105640
--- Comment #4 from Jakub Jelinek ---
What does LLVM implement?
Either I'm looking at a wrong place, or at least their testsuite coverage for
this is non-existing.
I see no sse nor avx substrings in clang/test/OpenMP/* (except for sse2020
which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105640
--- Comment #5 from Tobias Burnus ---
Regarding LLVM, I have no idea, but doing some searching, I do see:
* clang/test/OpenMP/declare_variant_clauses_ast_print.cpp:
//PRINT: #pragma omp declare variant(foo_v2) match(construct={dispatch},
device
