The current version of hash32 is about a year older than the one most recently released and has some behavior that is (incorrectly) flagged as undefined behavior (UB) by tools like Miri. This prevents any tool downstream of rbpf from using the rustc flags and tools like miri to identify UB as it will fail (xref https://github.com/rust-embedded-community/hash32/pull/14).
$ RUSTFLAGS="-Zstrict-init-checks" cargo +nightly test
thread 'elf::test::test_entrypoint' panicked at core/src/panicking.rs:221:5:
attempted to leave type `murmur3::Buffer` uninitialized, which is invalid
thread caused non-unwinding panic. aborting.
The current version of hash32 is about a year older than the one most recently released and has some behavior that is (incorrectly) flagged as undefined behavior (UB) by tools like Miri. This prevents any tool downstream of rbpf from using the rustc flags and tools like miri to identify UB as it will fail (xref https://github.com/rust-embedded-community/hash32/pull/14).
Upgrading hash32 fixes this.