You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An example of a project that would benefit from this is rapidfuzz which can be optimized for different x86_64-vX versions 1. Fedora is also investigating how to provide multiple versions of the architecture 2. I am not sure how to extend these to Python ecosystem though.
Afaiu, using glibc_hwcaps you can provide multiple variants of the library in a subpath like glibc-hwcaps/x86-64-v{2,3,4}/ and it would be automagically loaded. Not sure what the process is to get the libraries ready for it though, still need to investigate that. But then for compiled python modules it is more complicated because it would be the python library that determines which library file to load right?
An example of a project that would benefit from this is
rapidfuzz
which can be optimized for differentx86_64-vX
versions 1. Fedora is also investigating how to provide multiple versions of the architecture 2. I am not sure how to extend these to Python ecosystem though.Afaiu, using
glibc_hwcaps
you can provide multiple variants of the library in a subpath likeglibc-hwcaps/x86-64-v{2,3,4}/
and it would be automagically loaded. Not sure what the process is to get the libraries ready for it though, still need to investigate that. But then for compiled python modules it is more complicated because it would be the python library that determines which library file to load right?Footnotes
https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels ↩
https://fedoraproject.org/wiki/Changes/Optimized_Binaries_for_the_AMD64_Architecture ↩
The text was updated successfully, but these errors were encountered: