|
1 |
| -error: unsupported operation: can't call foreign function: __libc_current_sigrtmax |
2 |
| - --> CARGO_REGISTRY/.../mod.rs:LL:CC |
| 1 | +warning: integer-to-pointer cast |
| 2 | + --> CARGO_REGISTRY/.../imp_std.rs:LL:CC |
3 | 3 | |
|
4 |
| -LL | unsafe { __libc_current_sigrtmax() } |
5 |
| - | ^^^^^^^^^^^^^^^^^^^^^^^^^ can't call foreign function: __libc_current_sigrtmax |
| 4 | +LL | let mut waiter = (queue & !STATE_MASK) as *const Waiter; |
| 5 | + | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ integer-to-pointer cast |
6 | 6 | |
|
7 |
| - = help: this is likely not a bug in the program; it indicates that the program performed an operation that the interpreter does not support |
| 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. |
8 | 13 | = note: backtrace:
|
9 | 14 | note: inside `main` at $DIR/tokio_mvp.rs:LL:CC
|
10 | 15 | --> $DIR/tokio_mvp.rs:LL:CC
|
11 | 16 | |
|
12 | 17 | LL | #[tokio::main]
|
13 | 18 | | ^^^^^^^^^^^^^^
|
14 |
| - = note: this error originates in the attribute macro `tokio::main` (in Nightly builds, run with -Z macro-backtrace for more info) |
| 19 | + = note: this warning originates in the attribute macro `tokio::main` (in Nightly builds, run with -Z macro-backtrace for more info) |
| 20 | + |
| 21 | +warning: integer-to-pointer cast |
| 22 | + --> CARGO_REGISTRY/.../word_lock.rs:LL:CC |
| 23 | + | |
| 24 | +LL | (self & QUEUE_MASK) as *const ThreadData |
| 25 | + | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ integer-to-pointer cast |
| 26 | + | |
| 27 | +note: inside `main` at $DIR/tokio_mvp.rs:LL:CC |
| 28 | + --> $DIR/tokio_mvp.rs:LL:CC |
| 29 | + | |
| 30 | +LL | #[tokio::main] |
| 31 | + | ^ |
| 32 | + = note: this warning originates in the attribute macro `tokio::main` (in Nightly builds, run with -Z macro-backtrace for more info) |
15 | 33 |
|
16 |
| -note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace |
| 34 | +error: unsupported operation: cannot close epoll |
| 35 | + --> CARGO_REGISTRY/.../epoll.rs:LL:CC |
| 36 | + | |
| 37 | +LL | if let Err(err) = syscall!(close(self.ep)) { |
| 38 | + | ^^^^^^^^^^^^^^^^^^^^^^^^ cannot close epoll |
| 39 | + | |
| 40 | + = help: this is likely not a bug in the program; it indicates that the program performed an operation that the interpreter does not support |
| 41 | + = note: backtrace: |
| 42 | + = note: this error originates in the macro `syscall` (in Nightly builds, run with -Z macro-backtrace for more info) |
17 | 43 |
|
18 |
| -error: aborting due to previous error |
| 44 | +error: aborting due to previous error; 2 warnings emitted |
19 | 45 |
|
0 commit comments