bors 35a0617248 Auto merge of #98674 - RalfJung:miri-stacktrace-pruning, r=Mark-Simulacrum ... miri: prune some atomic operation and raw pointer details from stacktrace Since Miri removes `track_caller` frames from the stacktrace, adding that attribute can help make backtraces more readable (similar to how it makes panic locations better). I made them only show up with `cfg(miri)` to make sure the extra arguments induced by `track_caller` do not cause any runtime performance trouble. This is also testing the waters for whether the libs team is okay with having these attributes in their code, or whether you'd prefer if we find some other way to do this. If you are fine with this, we will probably want to add it to a lot more functions (all the other atomic operations, to start). Before: ``` error: Undefined Behavior: Data race detected between Atomic Load on Thread(id = 2) and Write on Thread(id = 1) at alloc1727 (current vector clock = VClock([9, 0, 6]), conflicting timestamp = VClock([0, 6])) --> /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:2594:23 | 2594 | SeqCst => intrinsics::atomic_load_seqcst(dst), | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data race detected between Atomic Load on Thread(id = 2) and Write on Thread(id = 1) at alloc1727 (current vector clock = VClock([9, 0, 6]), conflicting timestamp = VClock([0, 6])) | = 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: inside `std::sync::atomic::atomic_load::<usize>` at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:2594:23 = note: inside `std::sync::atomic::AtomicUsize::load` at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:1719:26 note: inside closure at ../miri/tests/fail/data_race/atomic_read_na_write_race1.rs:22:13 --> ../miri/tests/fail/data_race/atomic_read_na_write_race1.rs:22:13 | 22 | (&*c.0).load(Ordering::SeqCst) | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ``` After: ``` error: Undefined Behavior: Data race detected between Atomic Load on Thread(id = 2) and Write on Thread(id = 1) at alloc1727 (current vector clock = VClock([9, 0, 6]), conflicting timestamp = VClock([0, 6])) --> tests/fail/data_race/atomic_read_na_write_race1.rs:22:13 | 22 | (&*c.0).load(Ordering::SeqCst) | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data race detected between Atomic Load on Thread(id = 2) and Write on Thread(id = 1) at alloc1727 (current vector clock = VClock([9, 0, 6]), conflicting timestamp = VClock([0, 6])) | = 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: inside closure at tests/fail/data_race/atomic_read_na_write_race1.rs:22:13 ```		2022-07-24 06:46:46 +00:00
..
benches	Add unicode fast path to is_printable	2022-05-31 10:51:35 +02:00
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	Auto merge of #98674 - RalfJung:miri-stacktrace-pruning, r=Mark-Simulacrum	2022-07-24 06:46:46 +00:00
tests	Auto merge of #99491 - workingjubilee:sync-psimd, r=workingjubilee	2022-07-22 09:48:00 +00:00
Cargo.toml	Avoid use of rand::thread_rng in stdlib benchmarks	2022-05-02 00:08:21 -07:00