Thank you for the detailed answer!
The introspection sounds also interesting, but at least for the CPU side
the arch keyword "native" is already the ideal -march if one compiles
directly on the target architecture.
What I was thinking/dreaming of was a workflow close to:
(1) a user knows the exa
CMAKE_SYSTEM_PROCESSOR is a read-only variable that CMake will
populate to help inform projects what kind of platform they are
running on X86_64/ARM/PowerPC. It will not provide the level of detail
information needed to determine what specific architecture you should
specify. The best place to add
Dear CMake List,
we are building HPC software with CMake. In many cases, we find that the
performance of (auto)vectorization heavy code depends greatly on
specifying the exact processor generation for optimally tuned binaries.
That is no surprise, since a compiler's architecture flags just group
