about summary refs log tree commit diff
path: root/src/tools/miri
AgeCommit message (Collapse)AuthorLines
2025-05-23./miri bench: sort results alphabeticallyRalf Jung-11/+15
2025-05-23Merge from rustcThe Miri Cronjob Bot-3/+3
2025-05-23Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-05-22interpret: do not force_allocate all return placesRalf Jung-53/+54
2025-05-22Implement file cloning on WindowsRune Tynan-1/+97
2025-05-22enable isolated-stdin test on WindowsRalf Jung-1/+1
2025-05-22Implement file read/write on WindowsRune Tynan-81/+460
2025-05-21document that the entire test suite passes under freebsdRalf Jung-1/+1
2025-05-21run the full test suite under FreeBSDRalf Jung-2/+2
2025-05-21Implement FreeBSD syscall cpuset_getaffinity.LorrensP-2158466-2/+117
2025-05-21Merge pull request #4338 from RalfJung/FileDescriptionRalf Jung-2/+8
FileDescription: improve read/write docs
2025-05-21Add some track_caller info to precondition panicsBen Kimock-4/+1
2025-05-21FileDescription: improve read/write docsRalf Jung-2/+8
2025-05-21Merge pull request #4337 from RalfJung/ioRalf Jung-17/+25
test direct usage of io::{stdout,stderr,stdin}
2025-05-21test direct usage of io::{stdout,stderr,stdin}Ralf Jung-17/+25
2025-05-21Merge from rustcThe Miri Cronjob Bot-16/+10
2025-05-21Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-05-20Rename `cfg_match!` to `cfg_select!`Trevor Gross-3/+3
At [1] it was pointed out that `cfg_match!` syntax does not actually align well with match syntax, which is a possible source of confusion. The comment points out that usage is instead more similar to ecosystem `select!` macros. Rename `cfg_match!` to `cfg_select!` to match this. Tracking issue: https://github.com/rust-lang/rust/issues/115585 [1]: https://github.com/rust-lang/rust/issues/115585#issuecomment-2346307605
2025-05-20make std::intrinsic functions actually be intrinsicsRalf Jung-16/+10
2025-05-20Merge from rustcRalf Jung-6/+26
2025-05-20Preparing for merge from rustcRalf Jung-1/+1
2025-05-19Auto merge of #141255 - matthiaskrgr:rollup-ravsgen, r=matthiaskrgrbors-0/+20
Rollup of 6 pull requests Successful merges: - #131200 (Handle `rustc_query_system` cases of `rustc::potential_query_instability` lint) - #141244 (windows: document that we rely on an undocumented property of GetUserProfileDirectoryW) - #141247 (skip compiler tools sanity checks on certain commands) - #141248 (fix data race in ReentrantLock fallback for targets without 64bit atomics) - #141249 (introduce common macro for `MutVisitor` and `Visitor` to dedup code) - #141253 (Warning added when dependency crate has async drop types, and the feature is disabled) r? `@ghost` `@rustbot` modify labels: rollup
2025-05-19Rollup merge of #141248 - RalfJung:reentrant-lock-race, r=joboetMatthias Krüger-0/+20
fix data race in ReentrantLock fallback for targets without 64bit atomics See [Zulip](https://rust-lang.zulipchat.com/#narrow/channel/269128-miri/topic/reentrant.20lock.20failure.20on.20musl) for details: the address used to identify a thread might get lazily allocated inside `tls_addr()`, so if we call that *after* doing the `tls_addr.load()` it is too late to establish synchronization with prior threads that used the same address -- the `load()` thus races with the `store()` by that prior thread, and might hence see outdated values, and then the entire logic breaks down. r? `@joboet`
2025-05-19Merge pull request #4334 from RalfJung/GetUserProfileDirectoryW-issueRalf Jung-2/+2
GetUserProfileDirectoryW: reference issue regarding implementation details we rely on
2025-05-19GetUserProfileDirectoryW: reference issue regarding implementation details ↵Ralf Jung-2/+2
we rely on
2025-05-19run tests on mips-unknown-linux-gnuRalf Jung-22/+30
2025-05-19add this to Miri's trophy caseRalf Jung-0/+1
2025-05-19fix data race in ReentrantLock fallback for targets without 64bit atomicsRalf Jung-0/+19
2025-05-19Rollup merge of #141239 - RalfJung:dladdr-fname, r=NoratriebStuart Cook-4/+4
dladdr cannot leave dli_fname to be null There are two places in the repo calling `dladdr`, and they are inconsistent wrt their assumption of whether the `dli_fname` field can be null. Let's make them consistent. I see nothing in the docs that allows it to be null, but just to be on the safe side let's make this an assertion so hopefully we get a report if that ever happens.
2025-05-19add to_u64() helper method and use it where appropriateRalf Jung-26/+37
2025-05-19enable clippy::as_conversions to fully rule out as-castsRalf Jung-57/+61
2025-05-19dladdr cannot leave dli_fname to be nullRalf Jung-4/+4
2025-05-19Merge from rustcThe Miri Cronjob Bot-5/+7
2025-05-19Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-05-19Rollup merge of #140874 - mejrs:rads, r=WaffleLapkinStuart Cook-2/+2
make `rustc_attr_parsing` less dominant in the rustc crate graph It has/had a glob re-export of `rustc_attr_data_structures`, which is a crate much lower in the graph, and a lot of crates were using it *just* (or *mostly*) for that re-export, while they can rely on `rustc_attr_data_structures` directly. Previous graph: ![graph_1](https://github.com/user-attachments/assets/f4a5f13c-4222-4903-b56d-28c83511fcbd) Graph with this PR: ![graph_2](https://github.com/user-attachments/assets/1e053d9c-75cc-402b-84df-86229c98277a) The first commit keeps the re-export, and just changes the dependency if possible. The second commit is the "breaking change" which removes the re-export, and "explicitly" adds the `rustc_attr_data_structures` dependency where needed. It also switches over some src/tools/*. The second commit is actually a lot more involved than I expected. Please let me know if it's a better idea to back it out and just keep the first commit.
2025-05-18Auto merge of #140154 - Berrysoft:cygwin-host, r=jieyouxubors-1/+6
Cygwin support in rustc This PR builds host rustc targeting cygwin. - [x] https://github.com/rust-lang/stacker/pull/122 - [x] https://github.com/nagisa/rust_libloading/pull/173 - [x] https://github.com/Detegr/rust-ctrlc/pull/131 - [x] https://github.com/rust-random/getrandom/pull/654 - [x] https://github.com/msys2/MSYS2-packages/issues/5350 - [x] https://github.com/rust-lang/rust/pull/140886 - [x] https://github.com/rust-lang/rust/pull/140921 - [x] https://github.com/rust-lang/rust/pull/140973 Currently supported: * rustc * rustdoc * rustfmt * clippy Blocking: * cargo: blocked by https://github.com/rust-lang/socket2/pull/568 * rust-analyzer: needs `cargo update`, fixed upstream ``` $ rustc --version --verbose rustc 1.88.0-dev binary: rustc commit-hash: unknown commit-date: unknown host: x86_64-pc-cygwin release: 1.88.0-dev LLVM version: 20.1.4 ```
2025-05-18Rollup merge of #141214 - RalfJung:miri-sync, r=RalfJungLeón Orell Valerian Liehr-4/+11
Miri subtree update r? ``@ghost`` Fixes https://github.com/rust-lang/miri/issues/4328
2025-05-18Merge pull request #4330 from RalfJung/build-sysroot-bumpRalf Jung-3/+3
bump rustc-build-sysroot
2025-05-18Remove rustc_attr_data_structures re-export from rustc_attr_parsingmejrs-2/+2
2025-05-18bump rustc-build-sysrootRalf Jung-3/+3
2025-05-18Merge pull request #4322 from tiif/move_testRalf Jung-0/+4
Add more comments to libc-fs-with-isolation test
2025-05-18Add more comment to libc-fs-with-isolation testtiif-0/+4
2025-05-18attempt to make doctests work properly with old and new cargoRalf Jung-2/+5
2025-05-18Remove uses of `#[feature(avx512_target_feature)]`sayantn-4/+1
2025-05-18fmtThe Miri Cronjob Bot-1/+5
2025-05-18Merge from rustcThe Miri Cronjob Bot-58/+67
2025-05-18Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-05-17Auto merge of #141133 - matthiaskrgr:rollup-u8ndxyz, r=matthiaskrgrbors-58/+65
Rollup of 9 pull requests Successful merges: - #135808 (Implement Display for ``rustc_target::callconv::Conv``) - #137432 (Add as_ascii_unchecked() methods to char, u8, and str) - #139103 (deduplicate abort implementations) - #140917 (checktools.sh: fix bashism) - #141035 (turn lld warning on old gccs into info log) - #141118 (Enable rust-analyzer to go from query definition to the corresponding provider field) - #141121 (Only select true errors in `impossible_predicates`) - #141125 (check coroutines with `TypingMode::Borrowck` to avoid cyclic reasoning) - #141131 (Make some `match`es slightly more ergonomic in `librustdoc`) r? `@ghost` `@rustbot` modify labels: rollup
2025-05-17Rollup merge of #139103 - joboet:abort_dedup, r=tgross35Matthias Krüger-35/+43
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-17Rollup merge of #135808 - tiif:conv_display, r=workingjubileeMatthias Krüger-23/+22
Implement Display for ``rustc_target::callconv::Conv`` Follow up of https://github.com/rust-lang/rust/pull/133103#discussion_r1885552854
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-10 03:05:26 +0000