Open thezboe opened 1 year ago
It appears that configure.ac should be checking ax_cv_support_avx512f_ext
instead of ax_cv_have_avx512f_ext
, and likewise for the other SIMD options?
Good catch. As much as I hate to admit it, this is where CMake is useful...
Have you looked at zigbuild ? Or zig for that matter. It has a nice embedded build system and can cross compile (C, C++ and Zig) to tons of targets using the same binary.
Have you looked at zigbuild ? Or zig for that matter. It has a nice embedded build system and can cross compile (C, C++ and Zig) to tons of targets using the same binary.
Zig is pretty awesome for cross-compiling C, and as much as I hate CMake/autotools, using anything else is huge pain for downstream users.
I have looked into zig! Supports built-in testing as well!
Good catch. As much as I hate to admit it, this is where CMake is useful...
CMake is great (IMO)! But checking for microarchitectures is still pretty niche. Earlier this year I added https://github.com/jgaeddert/liquid-dsp/pull/314 which added CMake build support for the previous release version. In it I used Google's awesome cpu_features library for detection of supported CPU instruction sets. You can see how I hooked it into the build configuration here. If there's interest I can resurrect this PR for the current release version 1.6.
It appears that the configure script checks for AVX512 support. In my case, the OS and processor support, but I have an ancient version of GCC that doesn't yet have the AVX512 options. The configure script correctly determines this:
But, the resulting makefile still tries to use the flags, resulting in error.