Miri always panics on aarch64 linux with 16k page size.

[i509VCB]

Trying to run miri on a aarch64 Linux system with a 16k page size (which is standard for ARM Macs on Linux). There are performance drawbacks to using 4k kernels (along with them being buggy).

Output:

thread 'main' panicked at src/tools/miri/cargo-miri/src/phases.rs:98:9:
failed to determine underlying rustc version of Miri (MIRI_BE_RUSTC="host" "/home/i509vcb/.rustup/toolchains/nightly-aarch64-unknown-linux-gnu/bin/miri"):
CommandError { stdout: "", stderr: "<jemalloc>: Unsupported system page size\n<jemalloc>: Unsupported system page size\nLLVM ERROR: out of memory\nAllocation failed\n" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The system in question is a M2 MacBook Air running the Asahi remix of Fedora 42.

As a workaround miri can be run inside of muvm

[i509VCB]

I think the issue is that jemalloc as used by miri is being built assuming 4k pages. jemalloc/jemalloc#467 is relevant.

[CathalMullan]

Should be fixed on the latest nightly thanks to rust-lang/rust#145353

[RalfJung]

@CathalMullan thanks!

Directly building Miri from source in this repo will likely still be broken. Seems quite unfortunate that this logic needs to be replicated in each build system rather than being in the jemalloc crate -- might be good to track this in https://crates.io/crates/tikv-jemalloc-sys as well.