Our configure.ac still includes checks for whether we can build assembly code for various SIMD extensions, and accepts option to enable use of assembly language code. This doesn't apply to our implementation of yespower. This old logic should be dropped.
If anything, we could want to detect actual presence of the XOP extensions (not merely being able to build code using them) and use those.
Our
configure.ac
still includes checks for whether we can build assembly code for various SIMD extensions, and accepts option to enable use of assembly language code. This doesn't apply to our implementation of yespower. This old logic should be dropped.If anything, we could want to detect actual presence of the XOP extensions (not merely being able to build code using them) and use those.