about summary refs log tree commit diff
path: root/src/tools/miri/tests/pass/function_calls
AgeCommit message (Collapse)AuthorLines
2025-08-19Support weak definitionsbjorn3-0/+39
When a symbol only has a weak definition, this definition will be picked. When a symbol has both a weak and a regular definition, the regular definition will be picked instead.
2025-03-17Fix miribjorn3-0/+2
2024-11-04miri: update ABI compat checks to accept Option-like typesRalf Jung-0/+24
2024-09-29let rustfmt format importsRalf Jung-3/+1
2024-09-16Bump ui testOli Scherer-1/+1
2024-08-26interpret: do not make const-eval query result depend on tcx.sessRalf Jung-11/+0
2024-08-18stabilize raw_ref_opRalf Jung-1/+0
2024-06-03Add more ABI test cases.Lokathor-2/+14
2024-05-08Use generic `NonZero`.Markus Reiter-4/+4
2024-03-02remove the ability to disable ABI checkingRalf Jung-26/+0
2024-02-26rename 'try' intrinsic to 'catch_unwind'Ralf Jung-1/+1
2023-12-26custom mir: make it clear what the return block isRalf Jung-1/+1
2023-11-18guarantee that char and u32 are ABI-compatibleRalf Jung-1/+5
2023-11-14Custom MIR: Support cleanup blocksTomasz Miąsko-1/+1
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-14const-eval: allow calling functions with targat features disabled at compile ↵Eduardo Sánchez Muñoz-0/+11
time in WASM This is not unsafe on WASM, see https://github.com/rust-lang/rust/pull/84988
2023-09-21deprecate -Zmiri-disable-abi-checkRalf Jung-0/+2
2023-09-12extra ABI tests, in particular for DispatchFromDynRalf Jung-6/+16
2023-09-12fmtThe Miri Conjob Bot-1/+3
2023-09-09implement and test ABI compatibility for transparent wrappers around NPO typesRalf Jung-5/+8
2023-09-09implement and test fn ptr ABI compatibility rulesRalf Jung-0/+5
2023-09-09interpret: change ABI-compat test to be type-based, so the test is ↵Ralf Jung-18/+21
consistent across targets
2023-08-31miri ABI check: fix handling of 1-ZST; don't accept sign differencesRalf Jung-11/+15
2023-08-31update abi_compat.rsRalf Jung-12/+3
2023-08-31more ABI compat testsRalf Jung-12/+48
2023-08-31fmtRalf Jung-1/+1
2023-08-31Merge from rustcRalf Jung-2/+28
2023-08-30miri function ABI check: specifically look for repr(transparent)Ralf Jung-0/+4
2023-08-30interpret: make sure we accept transparent newtypes as ABI-compatibleRalf Jung-1/+23
also we were missing the case for Vector arguments, so handle those as well
2023-08-29fmtThe Miri Conjob Bot-4/+6
2023-08-24miri ABI compatibility check: accept u32 and i32Ralf Jung-0/+27
2023-08-19custom_mir: change Call() terminator syntax to something more readableRalf Jung-1/+1
2023-07-16miri: fail when calling a function that requires an unavailable target featureEduardo Sánchez Muñoz-0/+12
miri will report an UB when calling a function that has a `#[target_feature(enable = ...)]` attribute is called and the required feature is not available. "Available features" are the same that `is_x86_feature_detected!` (or equivalent) reports to be available during miri execution (which can be enabled or disabled with the `-C target-feature` flag).
2023-07-11miri: protect Move() function arguments during the callRalf Jung-0/+25
2022-09-21Add 'src/tools/miri/' from commit '75dd959a3a40eb5b4574f8d2e23aa6efbeb33573'Oli Scherer-0/+103
git-subtree-dir: src/tools/miri git-subtree-mainline: 3f3167fb59341ac3240ca1774f48e8c053219131 git-subtree-split: 75dd959a3a40eb5b4574f8d2e23aa6efbeb33573