* Dominik Mierzejewski: > If upstream doesn't support runtime selection of SIMD-optimized code > paths based on CPU capabilities, you can build several versions and > have glibc handle that by putting each version in a special subdirectory > of /usr/lib64, e.g.: > /usr/lib64/haswell > /usr/lib64/haswell/avx512_1/ > > See > https://clearlinux.org/news-blogs/transparent-use-library-packages-optimized-intel-architecture > for some details. These are ill-defined unfortuantely and as such not very useful. For example, -march=haswell does not result in code that can be placed in a haswell subdirectory. I'm working with AMD and Intel to come up with a better subdirectory definition that also matches between GCC and glibc. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
