It’s quite comprehensive, and though it may not be ready for cross-compiling (still testing that, but I have to learn how to cross compile first!), it does appear to support native optimizations for embedded architectures. Here is my concern, the following flags are generated:
I am concerned only because these flags will be a part of the PUBLIC compile features of a library, Eigen is the main math library backend as well as there are some templated image conversion routines that use SSE2 intrinsics to operate in my library. Having that many additional flags could ultimately lead to undesirable consequences such as command line arguments being too long?
I’m currently reworking it so that just the highest version (e.g. -mavx2) is used, but I’m not sure if I should even be worried about this.