about summary refs log tree commit diff
path: root/src/bootstrap
AgeCommit message (Collapse)AuthorLines
2025-05-18tools-aux ci runner: also cross-test doctestsRalf Jung-11/+9
2025-05-17bootstrap: bump windows tooklensy-65/+11
2025-05-16bump bootstrap cc-rs to `1.2.23`onur-ozkan-3/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-15Update IDEs to use rustfmt 2024, fix Zed settingsChai T. Rex-0/+4
- Update IDE `rust-analyzer` settings to use 2024 rather than 2021. - Fix Zed settings by removing `${workspaceFolder}/` from paths.
2025-05-15Rollup merge of #141027 - onur-ozkan:simpler-rustfmt-initialization, ↵Matthias Krüger-50/+12
r=albertlarsan68 remove `RustfmtState` to reduce `initial_rustfmt` complexity The current use of `RustfmtState` doesn't serve its main purpose as it never does the lazy evaulation since `Build::build` forces it to be ready on the early stage. If we want rustfmt to be ready on the early stage, we don't need to have `RustfmtState` complexity at all.
2025-05-15Fix exe() to make rustc wrapper happy王宇逸-1/+1
2025-05-15Experimental cygwin support in rustc王宇逸-4/+4
Co-authored-by: Ookiineko <chiisaineko@protonmail.com>
2025-05-15remove `RustfmtState` to reduce `initial_rustfmt` complexityonur-ozkan-50/+12
The current use of `RustfmtState` doesn't serve its main purpose as it never does the lazy evaulation since `Build::build` forces it to be ready on the early stage. If we want rustfmt to be ready on the early stage, we don't need to have `RustfmtState` complexity at all. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-14replace `cc_detect::cc2ar` with `cc::try_get_archiver`onur-ozkan-145/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-14Update rustix to 1.0.7 for bootstrap王宇逸-2/+2
2025-05-13Auto merge of #140887 - pietroalbini:pa-bootstrap-update, r=compiler-errorsbors-42/+39
Stage0 bootstrap update This PR [follows the release process](https://forge.rust-lang.org/release/process.html#master-bootstrap-update-tuesday) to update the stage0 compiler. The only thing of note is https://github.com/rust-lang/rust/commit/58651d1b316e268fac2100c3ae37bb502a36b8ba, which was flagged by clippy as a correctness fix. I think allowing that lint in our case makes sense, but it's worth to have a second pair of eyes on it. r? `@Mark-Simulacrum`
2025-05-13Format and skip formatting for pinMichael Goulet-2/+1
2025-05-12./x clippy ci --fixPietro Albini-40/+39
2025-05-12x86_64-lynx-lynxos178 is now present in the stage0Pietro Albini-1/+0
2025-05-12Silence warning in default compiler bootstrap settingsYotam Ofek-2/+0
2025-05-12update default condition of llvm-tools for install steponur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-12update llvm-tools copying logic for dist steponur-ozkan-12/+21
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-11Rollup merge of #140886 - Berrysoft:update-bootstrap-lock, r=jieyouxuLeón Orell Valerian Liehr-33/+13
Update deps of bootstrap for Cygwin This PR just runs ``` cargo update fd-lock xattr libc errno ``` It reduces dependency on `rustix 0.38.40` and updates `libc` & `errno`. Now it compiles successfully on Cygwin:)
2025-05-10Fix download of GCC from CI on non-nightly channelsJakub Beránek-1/+2
2025-05-10Update deps of bootstrap for Cygwin王宇逸-33/+13
2025-05-08bootstrap: more consistent use of `...` when citing configuration snippetsRalf Jung-2/+2
2025-05-08add change-entry for `x run rustfmt`onur-ozkan-0/+5
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-08implement `x run rustfmt`onur-ozkan-0/+55
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-07do not allow stage > 0 on `x fmt`onur-ozkan-1/+6
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-06bootstrap: Add check/test/run steps for src/tools/coverage-dumpZalathar-0/+98
This also causes the coverage-dump unit tests to run in CI and `./x test` by default.
2025-05-05Rollup merge of #140670 - onur-ozkan:129959, r=KobzolGuillaume Gomez-1/+1
calculate step duration in a panic-safe way obvious/self-explanatory change. Fixes #129959
2025-05-05Rollup merge of #140636 - onur-ozkan:panic-tracker-for-t-macro, r=KobzolGuillaume Gomez-5/+26
implement `PanicTracker` to track `t` panics Trying to understand panics triggered by `t` macro is very exhausting (especially on CI failures) because it doesn't provide any information about where the macro was originally invoked. This change adds that missing information when an inner call inside the `t` macro panics. Resolves #137557
2025-05-05Rollup merge of #140357 - onur-ozkan:133840, r=clubby789Guillaume Gomez-9/+11
bypass linker configuration and cross target check on `x check` I was going to handle this using the untracked env approach, but I realized it somehow doesn't regress https://github.com/rust-lang/rust/issues/130108 anymore... Anyway, if it works, it works. 😄 No need to dig deeper but my guess is we moved some cache-invalidating env from these functions to others. Fixes https://github.com/rust-lang/rust/issues/133840 try-job: aarch64-apple
2025-05-05calculate step duration in a panic-safe wayonur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-05update `cc_detect` testsonur-ozkan-6/+6
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-04implement `PanicTracker` to track `t` panicsonur-ozkan-5/+26
Trying to understand panics triggered by `t` macro calls is very exhausting (especially on CI failures) because it doesn't provide any information about where the macro was originally invoked. This change adds that missing information when an inner call inside the `t` macro panics. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-03Rollup merge of #140582 - GuillaumeGomez:update-sysinfo, r=KobzolMatthias Krüger-16/+131
Update sysinfo to `0.35.0` in bootstrap and `tools/opt-dist` This release is mostly bugfixes and code improvements.
2025-05-02Update sysinfo version to `0.35.0`Guillaume Gomez-16/+131
2025-05-01extend the list of registered dylibs on `test::prepare_cargo_test`onur-ozkan-3/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-04-30Rollup merge of #140438 - ferrocene:pa-debug-assertions-tools, r=KobzolMatthias Krüger-5/+22
Add `rust.debug-assertions-tools` option Before this PR, the two only options to configure the presence of debug assertions were the `rust.debug-assertions` and `rust.debug-assertions-std` options. The former applied to everything, and the latter allowed to override the setting just for the standard library. This combination of settings doesn't allow to enable debug assertions for the std and the compiler but not tools. Some tools (like Cargo) are not really meant to be executed with debug assertions enabled, and in Ferrocene we hit some debug assertions in it that are exclusively meant for its test suite. We'd thus like to enable debug assertions everywhere but in tools. This PR adds a `rust.debug-assertions-tools` setting that does exactly this.
2025-04-29Rollup merge of #140392 - Zalathar:goodbye-libtest, r=jieyouxuTrevor Gross-1/+1
compiletest: Remove the libtest-based executor and its dependency Now that #140288 has landed and the new compiletest executor is used by default, we can now move forward with removing the libtest dependency from compiletest. My hope is that after landing this, we can configure bootstrap to build compiletest with the pre-built stage0 library by default, instead of the in-tree stage0 library. That would give the stage0 redesign one less thing to worry about. --- This PR has deliberately been kept small and simple, to make it easier to revert if necessary. Further cleanup can take palce after we're confident that it won't need to be reverted. r? jieyouxu Blocker for https://github.com/rust-lang/rust/pull/119899
2025-04-29add `rust.debug-assertions-tools` optionPietro Albini-5/+22
2025-04-28Make bootstrap git tests more self-containedJakub Beránek-0/+3
2025-04-28compiletest: Remove the libtest-based executor and its dependencyZalathar-1/+1
This patch has deliberately been kept small and simple, to make it easier to revert if necessary. Further cleanup can take palce after we're confident that it won't need to be reverted.
2025-04-28add a FIXMEonur-ozkan-2/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-04-27bypass linker configuration and cross target check on `x check`onur-ozkan-1/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-04-25Rollup merge of #140006 - onur-ozkan:138778, r=onur-ozkanMatthias Krüger-5/+50
ensure compiler existance of tools on the dist step Fixes https://github.com/rust-lang/rust/issues/138778 with a coverage on https://github.com/rust-lang/rust/issues/138123 and https://github.com/rust-lang/rust/issues/138004. try-job: dist-powerpc64le-linux
2025-04-24Rollup merge of #140191 - Kobzol:remove-git-repository-from-git-config, ↵Matthias Krüger-4/+0
r=jieyouxu Remove git repository from git config It is no longer needed after https://github.com/rust-lang/rust/pull/138591. We could even remove the `nightly_branch` field, but it still has one usage. r? ``@jieyouxu``
2025-04-24Rollup merge of #140232 - nnethercote:rm-unnecessary-clones, r=SparrowLiiMatthias Krüger-3/+3
Remove unnecessary clones r? `@SparrowLii`
2025-04-24Remove some unnecessary clones.Nicholas Nethercote-3/+3
I found these by grepping for `&[a-z_\.]*\.clone()`, i.e. expressions like `&a.b.clone()`, which are sometimes unnecessary clones, and also looking at clones nearby to cases like that.
2025-04-23Auto merge of #139983 - flip1995:clippy-subtree-update, r=Manishearthbors-4/+0
Clippy subtree update r? `@Manishearth` Cargo.lock update due to the Clippy version bump and because Clippy moved from rinja (unmaintained) to askama. Last sync was skipped due to the askama issue and me not getting to fixing this in time.
2025-04-23Remove `git_repository` field from `GitConfig`Jakub Beránek-4/+0
It is no longer needed after a recent refactoring.
2025-04-22tidy: Remove rinja deps from proc_macro_depsPhilipp Krones-4/+0
2025-04-20Use `--author-date-order` when looking up upstream commits to support ↵Jakub Beránek-2/+79
subtree synces
2025-04-20Make `git_dir` required in several git functionsJakub Beránek-9/+3
It was always called with `Some`, so no need to complicate it with `Option`.