-
Notifications
You must be signed in to change notification settings - Fork 13.4k
add miri-track-caller to more intrinsic-exposing methods #99690
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
Rollup of 7 pull requests Successful merges: - rust-lang#95040 (protect `std::io::Take::limit` from overflow in `read`) - rust-lang#95916 (kmc-solid: Use `libc::abort` to abort a program) - rust-lang#99494 (Use non-relocatable code in nofile-limit.rs test) - rust-lang#99581 (Improve error messages involving `derive` and `packed`.) - rust-lang#99643 (Add `sign-ext` target feature to the WASM target) - rust-lang#99659 (Use `VecMap::get` in `ConstraintLocator::check`) - rust-lang#99690 (add miri-track-caller to more intrinsic-exposing methods) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
adjust for more backtrace pruning The Miri side of rust-lang/rust#99690. Those messages are much nicer. :) And we also need error-pattern much less.
adjust for more backtrace pruning The Miri side of rust-lang/rust#99690. Those messages are much nicer. :) And we also need error-pattern much less.
adjust for more backtrace pruning The Miri side of rust-lang/rust#99690. Those messages are much nicer. :) And we also need error-pattern much less.
Follow-up to #98674: I went through the Miri test suite to find more functions that would benefit from Miri backtrace pruning, and this is what I found.
Basically anything that just exposes a potentially-UB intrinsic to the user should get this treatment.