-> detect it as ARM arch
-> detect SVE or fixed size SVE

• Wrap CPUID ?
• Other OS/Arch specific detection at runtime ?
• Must keep similar APIn just with if instead of if constexpr

Provides detectors for SIMD extension ans pseudo extensions

<iostream> pollutes assembly with _GLOBAL initialisation, which is annoying.

https://godbolt.org/z/1v8c5W

Integrate required files to provide Conan integration

We need dem continuous tests

I'm building with eve's clang_sde cmake. Should not be reported as amd true I think

-fsycl is probably detectable

spy::supports::fast_fma<T> must be a thing

we have to take this into account

The svtbl2 instructions seem to be not on all sve enabled processors, including the ones we care about.

Akin to: if constexpr(cpp_ > 11_cpp)

We want to know preferred size of the register.

I didn't find the equivalent for MSVC but please check.

Here is btw llvm defaulting to 32 bytes on avx512 https://reviews.llvm.org/D67259

Source:

• https://en.wikipedia.org/wiki/Power_ISA#Specifications
• https://godbolt.org/z/Pn97fj

PowerPC ISA specification make it so even if you "supports" VMX or VSX, some intrinsic may or may not be available.
vmx_ and vsx_ must be complemented by ppc_simd_xxx for each PPC ISA version that introduces some specific intrinsic.

Can you add information for the detection of Nvidia's CUDA compiler (nvcc)? See https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#nvcc-identification-macro

It would be nice to also be able to detect the CUDA compilation phases (host and device code generation). A caveat is that clang can also compile CUDA and uses different macros, see https://www.llvm.org/docs/CompileCudaWithLLVM.html#detecting-clang-vs-nvcc-from-code

Some template parameters have all-caps names such as VERSION or ISA (see include/eve/detail/spy.hpp:764) that:

• Look like preprocessor variables
• Are already be defined in some cases

I think it's reasonable to change those names to avoid collisions since VERSION is a commonly defined variable, my suggestion would be to add a prefix like SPY_ or _SPY_ and/or change naming style altogether, as the all caps style might suggest they are preprocessor variables.

See https://emscripten.org/docs/compiling/Building-Projects.html#detecting-emscripten-in-preprocessor

I don't know what do you do in SPY and what you don't.

I need a:

  constexpr bool asan_enabled
  constexpr bool tsan_enabled

Maybe

constexpr bool sanitizers_enabled

I also need DISABLE_SAITIZERS macro.

Here is what I wrote to do it (didn't test on MSVC)

#if defined(__has_feature)
#  if __has_feature(address_sanitizer) or __has_feature(thread_sanitizer)
#       define EVE_SANITZERS_ARE_ON
#  endif  // __has_feature
#endif

#if defined(EVE_SANITZERS_ARE_ON)
  constexpr bool sanitizers_are_on = true;

#undef EVE_SANITZERS_ARE_ON

#else
  constexpr bool sanitizers_are_on = false;
#endif

And

#if defined(SPY_COMPILER_IS_CLANG) or defined(SPY_COMPILER_IS_GCC)
#define DISABLE_SANITIZERS __attribute__((no_sanitize_address)) __attribute__((no_sanitize_thread))
#elif defined(SPY_COMPILER_IS_MSVC)
#define DISABLE_SANITIZERS __declspec(no_sanitize_address)
#else
#define DISABLE_SANITIZERS
#endif