tests/fail/data_race/write_write_race_stack.stderr

error: Undefined Behavior: Data race detected between (1) non-atomic write on thread `unnamed-ID` and (2) non-atomic write on thread `unnamed-ID` at ALLOC
  --> tests/fail/data_race/write_write_race_stack.rs:LL:CC
   |
LL | ...   stack_var = 1usize;
   |       ^^^^^^^^^^^^^^^^^^ (2) just happened here
   |
help: and (1) occurred earlier here
  --> tests/fail/data_race/write_write_race_stack.rs:LL:CC
   |
LL |             *pointer.load(Ordering::Acquire) = 3;
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   = 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: this is on thread `unnamed-ID`
note: the current function got called indirectly due to this code
  --> tests/fail/data_race/write_write_race_stack.rs:LL:CC
   |
LL |           let j1 = spawn(move || {
   |  __________________^
LL | |             let ptr = ptr; // avoid field capturing
...  |
LL | |             stack_var
LL | |         });
   | |__________^

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to 1 previous error