fork/rust
git clone https://git.julia.blue/fork/rust
3bcad65fbf6
master
1warning: integer-to-pointer cast 2 --> $DIR/munmap.rs:LL:CC 3 | 4LL | / libc::munmap( 5LL | | 6LL | | // Some high address we surely have not allocated anything at 7LL | | ptr::invalid_mut(1 << 30), 8LL | | 4096, 9LL | | ) 10 | |_________^ integer-to-pointer cast 11 | 12 = help: This program is using integer-to-pointer casts or (equivalently) `ptr::from_exposed_addr`, 13 = help: which means that Miri might miss pointer bugs in this program. 14 = help: See https://doc.rust-lang.org/nightly/std/ptr/fn.from_exposed_addr.html for more details on that operation. 15 = help: To ensure that Miri does not miss bugs in your program, use Strict Provenance APIs (https://doc.rust-lang.org/nightly/std/ptr/index.html#strict-provenance, https://crates.io/crates/sptr) instead. 16 = help: You can then pass the `-Zmiri-strict-provenance` flag to Miri, to ensure you are not relying on `from_exposed_addr` semantics. 17 = help: Alternatively, the `-Zmiri-permissive-provenance` flag disables this warning. 18 = note: BACKTRACE: 19 = note: inside `main` at $DIR/munmap.rs:LL:CC 20 21error: unsupported operation: Miri only supports munmap on memory allocated directly by mmap 22 --> $DIR/munmap.rs:LL:CC 23 | 24LL | / libc::munmap( 25LL | | 26LL | | // Some high address we surely have not allocated anything at 27LL | | ptr::invalid_mut(1 << 30), 28LL | | 4096, 29LL | | ) 30 | |_________^ Miri only supports munmap on memory allocated directly by mmap 31 | 32 = help: this is likely not a bug in the program; it indicates that the program performed an operation that the interpreter does not support 33 = note: BACKTRACE: 34 = note: inside `main` at $DIR/munmap.rs:LL:CC 35 36note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace 37 38error: aborting due to previous error; 1 warning emitted 39