about summary refs log tree commit diff
path: root/src/tools/miri
AgeCommit message (Collapse)AuthorLines
2025-07-16Merge pull request #4456 from nia-e/trace-incorporate-eventsRalf Jung-25/+314
trace: incorporate events
2025-07-16update comment to reference legacy `.ctors` sectionIbraheem Ahmed-1/+1
Co-authored-by: Ralf Jung <post@ralfj.de>
2025-07-16hook up native-lib bitsNia Espera-25/+314
2025-07-16Make frame spans appear on a separate trace lineStypox-21/+51
This was done by making the tracing_chrome tracing layer check if "tracing_separate_line" was in the arguments of a span, and act accordingly.
2025-07-15add test for global constructorsIbraheem Ahmed-0/+43
2025-07-15add support for global constructors (i.e. life before main)Ibraheem Ahmed-32/+165
2025-07-15Merge pull request #4469 from Patrick-6/add-spinloop-hintsRalf Jung-15/+31
Add std::hint::spin_loop() to tests
2025-07-15Make spin function naming more consistentPatrick-6-17/+17
2025-07-15Merge pull request #4452 from Stypox/trace-borrow-trackerRalf Jung-1/+62
Add tracing spans to borrow tracker functions
2025-07-15Add InterpCx::fn_abi_of_instance/_fn_ptr with tracing, shadowing FnAbiOfStypox-1/+1
2025-07-15Add tracing calls to borrow tracker under the same nameStypox-0/+18
... but the function name is specified in the arguments, see https://github.com/rust-lang/miri/pull/4452#discussion_r2204958019
2025-07-15Add enter_trace_span! that checks #[cfg("tracing")]Stypox-1/+44
Includes a custom syntax shortand to enter_trace_span! with NAME::SUBNAME. MaybeEnteredTraceSpan is `pub use`d in lib.rs to make it available also in bin/, just in case.
2025-07-15Add std::hint::spin_loop()Patrick-6-6/+22
2025-07-15Merge from rustcThe Miri Cronjob Bot-1/+2
2025-07-15Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-07-14Auto merge of #143745 - flip1995:clippy-subtree-update, r=Manishearthbors-0/+1
Clippy subtree update r? `@Manishearth` Cargo.lock update due to `ui_test` bump and restructure.
2025-07-14Rollup merge of #143710 - joshtriplett:random-updates, r=joshtriplettSamuel Tardieu-1/+1
Updates to random number generation APIs Updates based on discussions about random number generation. - Add comment on `RandomSource::fill_bytes` about multiple calls, to allow efficient implementations for random sources that generate a word at a time. - Drop the `Random` trait in favor of `Distribution<T>`, which will let people make calls like random(1..=6), and which allows for future expansion to non-uniform distributions, as well as floating-point. (For now, this is only implemented for `RangeFull`, to get the interface in place. Subsequent PRs will implement it for other range types.)
2025-07-14Merge from rustcThe Miri Cronjob Bot-3/+6
2025-07-14Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-07-13Rollup merge of #143634 - nia-e:init-and-wildcards, r=RalfJungMatthias Krüger-3/+4
interpret/allocation: expose init + write_wildcards on a range Part of https://github.com/rust-lang/miri/pull/4456, so that we can mark down when a foreign access to our memory happened. Should this also move `prepare_for_native_access()` itself into Miri, given that everything there can be implemented on Miri's side? r? `````@RalfJung`````
2025-07-12fix clippy_test_deps workspace handlingRalf Jung-0/+1
2025-07-12./x test miri: fix cleaning the miri_ui directoryRalf Jung-0/+2
2025-07-12readme: update strict provenance linkRalf Jung-3/+3
2025-07-11Update miri for change to random APIJosh Triplett-1/+1
2025-07-10interpret/allocation: expose init + write_wildcards on a rangeNia Espera-3/+4
2025-07-10silence clippyRalf Jung-0/+1
2025-07-10fmtThe Miri Cronjob Bot-1/+3
2025-07-10Merge from rustcThe Miri Cronjob Bot-2/+10
2025-07-10Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-07-09miri: fix out-of-bounds error for ptrs with negative offsetsRalf Jung-0/+53
2025-07-09various native-lib-trace-related fixupsNia Espera-338/+312
Co-Authored-By: Ralf Jung <post@ralfj.de>
2025-07-08Implement enter_trace_span() in MiriMachineStypox-2/+10
2025-07-08Merge pull request #4454 from RalfJung/data_structureOli Scherer-25/+26
move our data structures into a central location
2025-07-08Merge from rustcRalf Jung-16/+16
2025-07-08Preparing for merge from rustcRalf Jung-1/+1
2025-07-07move our data structures into a central locationRalf Jung-25/+26
2025-07-07Rollup merge of #143528 - RalfJung:stack-pop-cleanup, r=oli-obk许杰友 Jieyou Xu (Joe)-16/+16
interpret: rename StackPopCleanup The name `StackPopCleanup` stopped making sense a long time ago IMO -- in the common case, it has nothing to do with "cleanup", and everything with where the program should jump next. If we didn't have unwinding this would be just the return block, but given that we do have unwinding I figured maybe "continuation" would be a good name. This comes up in [continuation-passing style](https://en.wikipedia.org/wiki/Continuation-passing_style) and refers to where the program will *continue* when a function is done. So from a PL perspective it is the most fitting term I think -- but it may be too jargony. r? `@oli-obk` what do you think?
2025-07-07Merge pull request #4450 from RalfJung/unwind-payloadsRalf Jung-157/+169
Unwinding != panicking
2025-07-07split unwinding logic from panic logicRalf Jung-152/+164
2025-07-07Merge from rustcThe Miri Cronjob Bot-0/+192
2025-07-07Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-07-06Auto merge of #141829 - dvdsk:sleep_until_linux, r=cuviper,RalfJungbors-0/+192
Specialize sleep_until implementation for unix (except mac) related tracking issue: https://github.com/rust-lang/rust/issues/113752 Supersedes https://github.com/rust-lang/rust/pull/118480 for the reasons see: https://github.com/rust-lang/rust/issues/113752#issuecomment-2902594469 Replaces the generic catch all implementation with target_os specific ones for: linux/netbsd/freebsd/android/solaris/illumos etc. Other platforms like wasi, macos/ios/tvos/watchos and windows will follow in later separate PR's (once this is merged).
2025-07-06sleep_until: add clock_nanosleep support to Miridvdsk-0/+192
The clock_nanosleep support is there to allow code using `sleep_until` to run under Miri. Therefore the implementation is minimal. - Only the clocks REALTIME and MONOTONIC are supported. The first is supported simply because it was trivial to add not because it was needed for sleep_until. - The only supported flag combinations are no flags or TIMER_ABSTIME only. If an unsupported flag combination or clock is passed in this throws unsupported.
2025-07-06rename panic_paylods → unwind_payloadsRalf Jung-7/+7
2025-07-06interpret: rename StackPopCleanupRalf Jung-16/+16
2025-07-05Merge pull request #4444 from devnexen/filemetadata_updRalf Jung-4/+22
shims::fs adding more fields to FileMetadata
2025-07-05minor cleanupRalf Jung-9/+4
2025-07-05shims::fs adding more fields to FileMetadataDavid Carlier-4/+27
addressing, partially at least, FIXME comment and targetting unixes, adding device, user and group ids.
2025-07-05miri-script: set msrv so clippy doesn't suggest too-new featuresRalf Jung-2/+1
2025-07-05fmtRalf Jung-1/+3