blob: 890bacd58d4dda07dc2e53d3d4a457a543c2b3e6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
error: Undefined Behavior: Data race detected between (1) non-atomic write on thread `unnamed-ID` and (2) non-atomic write on thread `main` at ALLOC
--> tests/fail/data_race/fence_after_load.rs:LL:CC
|
LL | unsafe { V = 2 }
| ^^^^^ (2) just happened here
|
help: and (1) occurred earlier here
--> tests/fail/data_race/fence_after_load.rs:LL:CC
|
LL | unsafe { V = 1 }
| ^^^^^
= help: this indicates a bug in the program: it performed an invalid operation, and caused Undefined Behavior
= help: see https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html for further information
= note: BACKTRACE (of the first span):
= note: inside `main` at tests/fail/data_race/fence_after_load.rs:LL:CC
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
error: aborting due to 1 previous error
|
