fork/rust

git clone https://git.julia.blue/fork/rust

borsAuto merge of #103046 - JanBeh:PR_clarify_cmp_terminology, r=workingjubilee3bcad65fbf6

master
1.6 KiB29 linesraw
1warning: integer-to-pointer cast
2  --> $DIR/munmap_partial.rs:LL:CC
3   |
4LL |         libc::munmap(ptr, 1);
5   |         ^^^^^^^^^^^^^^^^^^^^ integer-to-pointer cast
6   |
7   = help: This program is using integer-to-pointer casts or (equivalently) `ptr::from_exposed_addr`,
8   = help: which means that Miri might miss pointer bugs in this program.
9   = help: See https://doc.rust-lang.org/nightly/std/ptr/fn.from_exposed_addr.html for more details on that operation.
10   = 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.
11   = help: You can then pass the `-Zmiri-strict-provenance` flag to Miri, to ensure you are not relying on `from_exposed_addr` semantics.
12   = help: Alternatively, the `-Zmiri-permissive-provenance` flag disables this warning.
13   = note: BACKTRACE:
14   = note: inside `main` at $DIR/munmap_partial.rs:LL:CC
15
16error: unsupported operation: Miri only supports munmap calls that exactly unmap a region previously returned by mmap
17  --> $DIR/munmap_partial.rs:LL:CC
18   |
19LL |         libc::munmap(ptr, 1);
20   |         ^^^^^^^^^^^^^^^^^^^^ Miri only supports munmap calls that exactly unmap a region previously returned by mmap
21   |
22   = help: this is likely not a bug in the program; it indicates that the program performed an operation that the interpreter does not support
23   = note: BACKTRACE:
24   = note: inside `main` at $DIR/munmap_partial.rs:LL:CC
25
26note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
27
28error: aborting due to previous error; 1 warning emitted
29