Closed alexcrichton closed 2 years ago
This passes for me on main, but fails on CI.
Using stable-x86_64-unknown-linux-gnu unchanged - rustc 1.60.0 (7737e0b5c 2022-04-04)
.
This might be microarch specific, or nondeterminstic (perhaps memory layout dependent?).
I'm running on a AMD Ryzen 7 2700X.
I can reproduce this locally. Investigating.
I tracked down the segfault issue, and it's fixed in zlib-ng upstream, by commit a39e323a4db80a57feecf2ae212c08070234050c ("Added memory alignment compensation functions for users who may be using custom allocators that don't align on the same boundary zlib-ng expects.").
I tried updating to current zlib-ng, but that resulted in a different testsuite failure, which I tracked down and reported as https://github.com/zlib-ng/zlib-ng/pull/1258 .
I'm going to submit a PR updating to a version of zlib-ng sufficiently new to fix this issue, but prior to the introduction of the new issue.
I've uploaded a fixed libz-sys.
cc @joshtriplett this may interest you, it like the
zlib-ng-compat
feature is broken onmain
Locally in gdb I see:
which looks like an unaligned pointer passed to the
_mm_load_si128
intrinsic. This is perhaps related to a recent zlib-ng update in the libz-sys crate?