Closed ashbob999 closed 3 months ago
As a side note, what is the reason for disabling the built-in functions for testing/benchmarks (I know it's needed for the standalone binary)?
Because these flags are also supported by Clang, but I didn't modify them because I wasn't sure what there purpose was.
@ashbob999, we should avoid built-ins on all compilers, to benchmark the throughput of pure StringZilla implementations that wouldn't call LibC for some operations under the hood.
@ashbob999, we should avoid built-ins on all compilers, to benchmark the throughput of pure StringZilla implementations that wouldn't call LibC for some operations under the hood.
Ok, that makes sense. So we should add the options for Clang/AppleClang/MSVC as well.
Any reason the specific ones are eased instead of the general -fno-builtin
.
Would this decrease the performance of the other benchmarks?
:tada: This PR is included in version 3.7.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
set(CMAKE_CXX_STANDARD 17)
) after the custom one.-march
for Clang/AppleClang (-march=native
can be used, as long as we are not cross compiling). Which means that the Clang/MacOS workflows haveAVX2
enabled when running the test program.ARM64
backend.Fixes #124