Prepare for merging https://reviews.llvm.org/D116879 into LLVM,
which enables vectorization of sincos() via libmvec.
Compared to the other functions in libmvec, sincos() vectorisation
offers additional pitfalls as it returns two results via pointers.
Thus a test seems justified that checks the transformations performed
by llvm match the interface of the underlying vector library.
The test is run for any instruction set in {SSE, SSE2, AVX, AVX2, AVX512F}
supported by the CPU as well as with -march=native to improve coverage.
The supplied CMakeLists.txt only enables the check for -fveclib=libmvec on x86.
I leave enabling other vector libraries to people who can test those setups.
There is no check for successfull vectorization here, however a
regression test in the llvm repo already checks that.
Is this enough to ensure that the library is actually available on the system or could the compiler have the flag but the linker can't find libmvec?