Block a user
arm64: valgrind false positives in checkMaxBetweenExclusiveImpl with clang 21+ (csel definedness pessimization)
arm64: valgrind false positives in checkMaxBetweenExclusiveImpl with clang 21+ (csel definedness pessimization)
Closing since this isn't blocking us from running valgrind in arm anymore since 6fed1332121fe010f6ac88f6995589b1e47d23b5
aarch64 Node16 SIMD helpers load uninitialized child slots
This was all written under the assumption that the rules were basically what valgrind tracks, but after reading https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/n4849.pdf#subsection.6.7.4…
We write it in assembly because it's not UB in assembly. Not because MSAN doesn't track it.
Run valgrind in arm64 release in CI
arm64: valgrind false positives in checkMaxBetweenExclusiveImpl with clang 21+ (csel definedness pessimization)
Turns out according to https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/n4849.pdf#subsection.6.7.4 the source is actually UB. Still potentially a good valgrind improvement though
Add MemorySanitizer build to CI
Add a memory sanitizer build to CI
Add a memory sanitizer build to CI