tests::bytes test fails on sparc64

This is reproducible on sparc64 on Linux:

glaubitz@cfarm202:~/rustc-hash$ cargo build --release
    Updating crates.io index
     Locking 14 packages to latest compatible versions
      Adding rand v0.8.6 (available: v0.10.1)
   Compiling rustc-hash v2.1.2 (/home/glaubitz/rustc-hash)
    Finished `release` profile [optimized] target(s) in 1.10s
glaubitz@cfarm202:~/rustc-hash$ cargo test
   Compiling rustc-hash v2.1.2 (/home/glaubitz/rustc-hash)
    Finished `test` profile [unoptimized + debuginfo] target(s) in 4.89s
     Running unittests src/lib.rs (target/debug/deps/rustc_hash-d513507c1662bed2)

running 7 tests
test seeded_state::tests::cloned_seeded_states_are_equal ... ok
test seeded_state::tests::different_states_are_different ... ok
test seeded_state::tests::same_seed_produces_same_hasher ... ok
test tests::unsigned ... ok
test tests::signed ... ok
test tests::bytes ... FAILED
test tests::with_seed_actually_different ... ok

failures:

---- tests::bytes stdout ----

thread 'tests::bytes' (199963) panicked at src/lib.rs:463:9:
assertion `left == right` failed
  left: 6513278015018369270
 right: 17606491139363777937
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    tests::bytes

test result: FAILED. 6 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass `--lib`
glaubitz@cfarm202:~/rustc-hash$

Access to this machine is possible through the GCC Compile Farm.

Start by running cargo test --lib on sparc64 Linux and inspect the failing tests::bytes assertion at src/lib.rs:463, comparing it with the passing unsigned and signed tests. Done means tests::bytes passes on sparc64 while the complete test suite remains green.