about summary refs log tree commit diff
path: root/src/tools
AgeCommit message (Collapse)AuthorLines
2025-05-23Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-05-23Normalize when checking for uninhabited types for pattern exhaustiveness ↵Chayim Refael Friedman-25/+81
checking
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-22Rollup merge of #141130 - mejrs:use_self, r=compiler-errorsMatthias Krüger-1/+1
rustc_on_unimplemented cleanups Addresses some of the fixmes from https://github.com/rust-lang/rust/pull/139091 and https://github.com/rust-lang/rust/pull/140307. - switch from `_Self` to `Self` in library - properly validate that arguments in the `on` filter and the format strings are actually valid See https://github.com/rust-lang/rustc-dev-guide/pull/2357 for the relevant documentation.
2025-05-22Remove rust-analyzer.vs from other editorsOli Scherer-24/+0
2025-05-22enable isolated-stdin test on WindowsRalf Jung-1/+1
2025-05-22Implement file read/write on WindowsRune Tynan-81/+460
2025-05-22Merge pull request #19842 from Veykril/push-zunlmrzpnrzkLukas Wirth-1/+1
minor: Support `transmute_unchecked` intrinsic for mir-eval
2025-05-22Support `transmute_unchecked` intrinsic for mir-evalLukas Wirth-1/+1
2025-05-22Merge pull request #19824 from ChayimFriedman2/lints-againLukas Wirth-164/+60
fix: Fix cache problems with lints level
2025-05-22Auto merge of #137198 - tgross35:cfg-match-rename, r=Amanieubors-3/+3
Rename `cfg_match!` to `cfg_select!` [`@Nemo157` pointed out](https://github.com/rust-lang/rust/issues/115585#issuecomment-2346307605) 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-22Rename `kw::Empty` as `sym::empty`.Nicholas Nethercote-4/+4
Because the empty string is not a keyword.
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-21Merge pull request #19839 from ChayimFriedman2/inlay-hints-attrLukas Wirth-5/+15
fix: Correctly set the span of the proc_macro crate's Group delimiters
2025-05-21Implement FreeBSD syscall cpuset_getaffinity.LorrensP-2158466-2/+117
2025-05-21internal: fix `integrated_benchmarks` to make actual editsDavid Barsky-8/+12
2025-05-21Correctly set the span of the proc_macro crate's Group delimitersChayim Refael Friedman-5/+15
Previously only the open delimiter's span was set, and this caused... weird problems.
2025-05-21Merge pull request #4338 from RalfJung/FileDescriptionRalf Jung-2/+8
FileDescription: improve read/write docs
2025-05-21Merge commit 'cadf98bb7d783e2ea3572446c3f80d3592ec5f86' into ↵Philipp Krones-4612/+6166
clippy-subtree-update
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-1374/+3459
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-20Auto merge of #141278 - lnicola:sync-from-ra, r=lnicolabors-1358/+3449
Subtree update of `rust-analyzer` r? `@ghost`
2025-05-20Merge pull request #19826 from lnicola/sync-from-rustLaurențiu Nicola-7444/+10058
minor: Sync from downstream
2025-05-20Bump rustc cratesLaurențiu Nicola-22/+29
2025-05-20Merge from rust-lang/rustLaurențiu Nicola-7423/+10030
2025-05-20Preparing for merge from rust-lang/rustLaurențiu Nicola-1/+1
2025-05-20make std::intrinsic functions actually be intrinsicsRalf Jung-16/+10
2025-05-20Merge from rustcRalf Jung-21/+44
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-19Fix cache problems with lints levelChayim Refael Friedman-164/+60
By removing the cache.
2025-05-19Merge pull request #19822 from Veykril/push-mzzluystvwlsLukas Wirth-49/+1
minor: Remote dangling file
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-19Rollup merge of #141117 - klensy:opt-dist-icf, r=KobzolStuart Cook-1/+1
opt-dist: fix deprecated BOLT -icf=1 option Replaced deprecated `-icf=1` BOLT option. Spotted in recent CI run (https://github.com/rust-lang-ci/rust/actions/runs/15080898417/job/42397253162): ``` BOLT-WARNING: specifying numeric value "1" for option -icf is deprecated ``` Change was added in https://github.com/llvm/llvm-project/pull/116275 Btw, now there also exist new option `-icf=safe`, will be nice to try it too.
2025-05-19Remote dangling fileLukas Wirth-49/+1
2025-05-19Merge pull request #19809 from flodiebold/push-txyotwlvvklnLukas Wirth-1/+17
internal: Catch panics in inference in analysis-stats
2025-05-19add to_u64() helper method and use it where appropriateRalf Jung-26/+37
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 17:32:08 +0000