about summary refs log tree commit diff
path: root/src/tools/miri/tests/fail/function_calls
AgeCommit message (Collapse)AuthorLines
2025-09-22TB: rename Active → Unique to match paperRalf Jung-14/+14
2025-09-02improve process::abort rendering in Miri backtracesRalf Jung-13/+9
2025-08-22miri: also detect aliasing of in-place argument and return placeRalf Jung-0/+95
2025-08-20bless new testsRalf Jung-0/+1
2025-08-20Merge ref 'f605b57042ff' from rust-lang/rustThe Miri Cronjob Bot-37/+129
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: f605b57042ffeb320d7ae44490113a827139b766 Filtered ref: c69d2743ed4676c4529ebb60b258f6c1273c9145 This merge was created using https://github.com/rust-lang/josh-sync.
2025-08-19God bless the testsJohannes Hostert-0/+5
2025-08-19miri: detect passing the same local twice as an in-place argumentRalf Jung-0/+92
2025-08-18interpret: fix in-place return place semantics when the return place ↵Ralf Jung-37/+37
expression is a local variable
2025-08-07Rollup merge of #144903 - Kivooeo:panic_handler-is-not-begin, r=m-ou-seTrevor Gross-4/+4
Rename `begin_panic_handler` to `panic_handler` Part of https://github.com/rust-lang/rust/issues/116005
2025-08-06Print thread ID in panic message if thread name is unknownTrevor Gross-7/+7
`panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print.
2025-08-04remove begin prefixKivooeo-4/+4
2025-08-03remove rust_ prefixesKivooeo-2/+2
2025-07-17Report the range of uninit bytes in CTFE errorsOli Scherer-4/+32
2025-06-07bless non-Linux testsRalf Jung-1/+1
2025-06-07diagnostics: do not repeat the entire message in the span labelRalf Jung-32/+32
2025-05-17Rollup merge of #139103 - joboet:abort_dedup, r=tgross35Matthias Krüger-3/+3
deduplicate abort implementations Currently, the code for process aborts is duplicated across `panic_abort` and `std`. This PR uses `#[rustc_std_internal_symbol]` to make the `std` implementation available to `panic_abort` via the linker, thereby deduplicating the code.
2025-05-15normalize abort calls in miri testsjoboet-3/+3
2025-03-12bless testtiif-12/+12
2025-03-12Implement Display by mapping Conv to ExternAbitiif-3/+3
2025-02-06some more argument checking cleanupRalf Jung-9/+9
2025-01-01Try to write the panic message with a single `write_all` callJohn Kåre Alsaker-0/+7
2024-12-13Fix miri testsEsteban Küber-10/+0
2024-09-16Bump ui testOli Scherer-115/+115
2024-08-29fix wasm testRalf Jung-0/+26
2024-08-24panicking: improve hint for Miri's RUST_BACKTRACE behaviorRalf Jung-5/+5
2024-08-18stabilize raw_ref_opRalf Jung-4/+0
2024-08-13remove the concept of a Call IDRalf Jung-10/+10
2024-08-07Merge from rustcThe Miri Cronjob Bot-3/+3
2024-08-06interpret: refactor function call handling to be better-abstractedRalf Jung-3/+3
2024-08-06add return-place-protection tail-call test, and fix previous testRalf Jung-39/+157
2024-06-19Remove c_unwind from tests and fix testsGary Guo-3/+1
2024-06-16std: move `sys_common::backtrace` to `sys`joboet-2/+2
2024-04-18when suggesting RUST_BACKTRACE=1, add a special note for Miri's env var ↵Ralf Jung-0/+5
isolation
2024-03-06Auto merge of #3340 - RalfJung:no-disable-abi-check, r=oli-obkbors-6/+2
remove the ability to disable ABI checking This got deprecated in https://github.com/rust-lang/miri/pull/3071, about half a year ago. `@rust-lang/miri` I think it's fine to remove this now.
2024-03-02Tree Borrows: print where the forbidden access happens; make tag tracking ↵Ralf Jung-8/+8
less verbose
2024-03-02remove the ability to disable ABI checkingRalf Jung-6/+2
2024-03-02print thread name in miri error backtracesRalf Jung-0/+2
2024-02-26rename 'try' intrinsic to 'catch_unwind'Ralf Jung-2/+2
2024-01-11std: update miri testsjoboet-4/+4
2023-12-26custom mir: make it clear what the return block isRalf Jung-27/+27
2023-11-24Bless Miri testsNilstrieb-30/+30
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-11-14Custom MIR: Support cleanup blocksTomasz Miąsko-27/+27
Cleanup blocks are declared with `bb (cleanup) = { ... }`. `Call` and `Drop` terminators take an additional argument describing the unwind action, which is one of the following: * `UnwindContinue()` * `UnwindUnreachable()` * `UnwindTerminate(reason)`, where reason is `ReasonAbi` or `ReasonInCleanup` * `UnwindCleanup(block)` Also support unwind resume and unwind terminate terminators: * `UnwindResume()` * `UnwindTerminate(reason)`
2023-10-09return_pointer_aliasing2 should also run with SBRalf Jung-2/+45
2023-10-09add test to ensure RET assignments do not get propagated on unwindingRalf Jung-0/+74
2023-10-05Tree Borrows: do not create new tags as 'Active'Ralf Jung-4/+28
2023-10-02add test for a function ABI mismatch due to target featuresRalf Jung-0/+50
2023-09-23Merge from rustcThe Miri Conjob Bot-2/+2
2023-09-21adjust how closure/generator types and rvalues are printedRalf Jung-2/+2
2023-09-21deprecate -Zmiri-disable-abi-checkRalf Jung-0/+2
2023-08-22fix some bad regex capture group references in test normalizationRalf Jung-2/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-12 14:39:14 +0000