about summary refs log tree commit diff
path: root/src/bootstrap
AgeCommit message (Collapse)AuthorLines
2025-01-12apply minor improvements on build_stamponur-ozkan-1/+4
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12migrate `program_out_of_date` to `BuildStamp::is_up_to_date`onur-ozkan-46/+20
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12add coverage for `BuildStamp::with_prefix`onur-ozkan-0/+16
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12fix an invalid prefix usage on enzymeonur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12fix compiler errorsonur-ozkan-2/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12migrate `generate_smart_stamp_hash`onur-ozkan-55/+55
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12add test coverage for `build_stamp` implementationonur-ozkan-0/+47
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12document `build_stamp` implementationonur-ozkan-6/+18
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12migrate `Builder::clear_if_dirty`onur-ozkan-30/+29
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12migrate helper stamp functionsonur-ozkan-141/+79
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12migrate `HashStamp` to `BuildStamp`onur-ozkan-66/+29
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12use `BuildStamp` instead of std paths and stringsonur-ozkan-69/+86
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-12implement `BuildStamp` that is stricter impl for build stampsonur-ozkan-2/+78
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-11don't use a string constantbinarycat-6/+5
2025-01-11clean up code related to the rustdoc-js test suitebinarycat-6/+7
2025-01-11allow rustdoc-js tests to be run at stage0binarycat-1/+4
this mirrors the behavior of rustdoc-js-std tests. previously this required COMPILETEST_FORCE_STAGE0.
2025-01-11ci: added ci format to test_renderRoss Sullivan-3/+49
2025-01-11Rollup merge of #135326 - onur-ozkan:target-specific-compiler-builtins, ↵Jacob Pratt-2/+27
r=jieyouxu support target specific `optimized-compiler-builtins` Makes it possible to control `optimized-compiler-builtins` for per target. This was raised in the [zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Building.20and.20packaging.20Rust.20with.20x86_64-unknown-uefi.20support/near/492765883) yesterday.
2025-01-11Rollup merge of #135301 - lolbinarycat:bootstrap-old-master-resurected, ↵Jacob Pratt-0/+3
r=onur-ozkan re-add a warning for old master branch, but with much simpler logic instead of calling into git or checking the modification time of files, simply print the warning if there is a very large number of "modified" files. also make the wording much softer, so false positives are less alarming. (warning was removed in https://github.com/rust-lang/rust/issues/134935)
2025-01-10never print the warning on CIbinarycat-1/+1
2025-01-10add change entry for `optimized-compiler-builtins`onur-ozkan-0/+5
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-10ensure `optimized_compiler_builtins` check for CI rustconur-ozkan-0/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-10add coverage for target specific valueonur-ozkan-1/+8
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-10make `optimized-compiler-builtins` target configurableonur-ozkan-1/+11
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-09re-add a warning for old master branch, but with much simpler logicbinarycat-0/+3
instead of calling into git or checking the modification time of files, simply print the warning if there is a very large number of "modified" files. also make the wording much softer, so false positives are less alarming.
2025-01-09bootstrap: `std::io::ErrorKind::CrossesDevices` is finally stablePavel Grigorenko-4/+1
2025-01-09Auto merge of #135268 - pietroalbini:pa-bump-stage0, r=Mark-Simulacrumbors-16/+9
Master bootstrap update Part of the release process. r? `@Mark-Simulacrum`
2025-01-09Rollup merge of #135256 - onur-ozkan:weird-mod-position, r=clubby789,jieyouxuMatthias Krüger-2/+2
Move `mod cargo` below the import statements Just caught that during a [bootstrap reading-club](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/.5BBRC.5D.20How.20do.20Steps.20and.20Paths.20work.3F) session.
2025-01-09Rollup merge of #135231 - Zalathar:test-step-notes, r=jieyouxuMatthias Krüger-0/+43
bootstrap: Add more comments to some of the test steps Some of the test steps have names that don't clearly indicate what they actually do. While there is ongoing experimental work to actually rename the steps (e.g. #135071), that's dependent on figuring out what the new names should actually be. In the meantime, we can still improve things by adding comments to help describe the steps, which will remain useful even after any renaming.
2025-01-08fmtPietro Albini-1/+1
2025-01-08applease clippyPietro Albini-8/+8
2025-01-08update cfg(bootstrap)Pietro Albini-8/+1
2025-01-08Move `mod cargo` below the import statementsonur-ozkan-2/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-08Revert "fix missing rustfmt and clippy for msi"Pietro Albini-30/+1
This reverts commit f5577a8174685aca342b9189e625648f25a23a20.
2025-01-08Revert "fix missing rustfmt for apple darwin"Pietro Albini-9/+3
This reverts commit 2316749ca954030afed6145342808a8c1ae29fac.
2025-01-08Add more comments to some of the test stepsZalathar-0/+43
2025-01-07Rollup merge of #135081 - mrkajetanp:jemalloc-64k, r=KobzolGuillaume Gomez-0/+9
bootstrap: Build jemalloc with support for 64K pages By default, jemalloc is built to only support the same page size as the host machine. Set an env variable so that jemalloc is built with support for page sizes up to 64K regardless of the host machine. r? `@Kobzol` Resolves #134563 Potentially resolves #133748 (needs verification) ---- Results from local rustc-perf testing below, within 0.5% on every metric except max-rss. AArch64: ![Screenshot 2025-01-03 at 5 53 13 pm](https://github.com/user-attachments/assets/71705c59-7d7b-4753-a184-8c784233e603) x86_64: ![Screenshot 2025-01-03 at 5 54 16 pm](https://github.com/user-attachments/assets/ea28aded-3b90-43f4-a965-b081b07b95ab)
2025-01-06bootstrap: Build jemalloc for AArch64 with support for 64K pagesKajetan Puchalski-0/+9
By default, jemalloc is built to only support the same page size as the host machine. For AArch64 targets, set an env variable so that jemalloc is built with support for page sizes up to 64K regardless of the host machine.
2025-01-06Rollup merge of #135097 - Zalathar:coverage-test-step, r=KobzolMatthias Krüger-120/+101
bootstrap: Consolidate coverage test suite steps into a single step Now that I have more understanding of bootstrap steps, and a renewed distaste for unnecessary macros, I have managed to express the subtleties of the `tests/coverage` test suite in a single step defined in ordinary code, with no need for helper macros. Deciding which modes to run is still a bit clunky due to limitations in existing ShouldRun/PathSet APIs, but I think it's a net improvement over having to declare several different steps to handle the suite path and aliases. The interaction with `--skip` isn't as nice as I'd like, but all of the known limitations are limitations that already existed in the previous implementation. One minor change is that by default compiletest is now invoked in `coverage-run` mode even when cross-compiling. However, in that situation compiletest still knows that it should skip all of the individual coverage-run tests. r? jieyouxu (or reassign)
2025-01-06Ensure generate-copyright is executed from the project root.Jonathan Pallant-0/+3
2025-01-06Consolidate coverage test suite steps into a single stepZalathar-120/+101
2025-01-04Auto merge of #135101 - workingjubilee:rollup-owp3czl, r=workingjubileebors-1/+1
Rollup of 6 pull requests Successful merges: - #135046 (turn rustc_box into an intrinsic) - #135061 (crashes: add latest batch of tests) - #135070 (std: sync to dep versions of backtrace) - #135088 (Force code generation in assembly generation smoke-tests) - #135091 (Bump backtrace to 0.3.75) - #135094 (bootstrap: If dir_is_empty fails, show the non-existent directory path) r? `@ghost` `@rustbot` modify labels: rollup
2025-01-04Rollup merge of #135094 - joshtriplett:bootstrap-show-nonexistent-dir, ↵Jubilee-1/+1
r=jieyouxu bootstrap: If dir_is_empty fails, show the non-existent directory path This should help when trying to debug issues.
2025-01-04bootstrap: make `is_path_in_submodule` return optional submodule path instead许杰友 Jieyou Xu (Joe)-15/+23
2025-01-04Rollup merge of #135066 - jieyouxu:check-run-make-support, r=clubby789Matthias Krüger-0/+6
bootstrap: support `./x check run-make-support` Mostly for working on `src/tools/run-make-support` locally.
2025-01-04Rollup merge of #135001 - Kobzol:bootstrap-mcp-510, r=onur-ozkanMatthias Krüger-2/+14
Allow using self-contained LLD in bootstrap In https://github.com/rust-lang/rust/pull/116278, I added a `"self-contained"` mode to the `rust.use-lld` bootstrap option, which was designed for using the built-in LLD for linking compiler artifacts. However, this was later reverted in https://github.com/rust-lang/rust/pull/118810. This PR brings the old logic back, which switches LLD in bootstrap from `-fuse-ld=lld` to [MCP510](https://github.com/rust-lang/compiler-team/issues/510)'s way of passing linker flags to enable LLD (both external and self-contained). So this does two changes: 1) Goes from `-fuse-ld=lld` to MCP510 2) Actually makes it possible to use the self-contained LLD to compile compiler artifacts Regarding the second commit: Since https://github.com/rust-lang/rust/pull/86113, we have been passing `-fuse-ld=lld` as a target flag to all tests when `use-lld = true` is enabled. This kind of worked for all tests, since it was just a linker argument, which has bypassed any compiler checks, and probably resulted only in some warning if the given target linker didn't actually support LLD. However, after the first commit, some tests actually start failing with this approach: ``` error: linker flavor `gnu-lld-cc` is incompatible with the current target | = note: compatible flavors are: llbc, ptx ``` So the second commit removes the passing of LLD flags as target flags to tests. I don't think that it's a good idea to pass specific compiler flags to all tests unconditionally, tbh. The doctest command from #86113 doesn't go through compiletest anymore, and doctests should be quite a lot faster since https://github.com/rust-lang/rust/pull/126245 in general. CC `@the8472` If someone has a beefy machine, it would be nice to test whether this doesn't regress test execution speed. How to do that: 1) Enable `rust.use-lld = true` and `rust.lld = true` in `config.toml` 2) Benchmark `./x test tests/ui --force-rerun` between `master` and this PR Once this is tested in the wild, I would like to make the self-contained LLD the default in CI, hopefully to make CI builds faster. r? `@onur-ozkan`
2025-01-04bootstrap: If dir_is_empty fails, show the non-existent directory pathJosh Triplett-1/+1
This should help when trying to debug issues.
2025-01-03Rollup merge of #135058 - onur-ozkan:path-resolution, r=jieyouxuMatthias Krüger-27/+76
refactor bootstrap path resolution Previously we removed paths as soon as we found the first intersection, which made it impossible to find other intersecting paths (and that is the reason of https://github.com/rust-lang/rust/issues/135022). This patch changes that by marking the intersecting paths instead, so we can collect them all and remove them together when needed. Which means, `x build compiler` would compile anything that ends or starts with `"compiler"` instead of picking the first matching `Step` from `builder::get_step_descriptions`. Fixes https://github.com/rust-lang/rust/issues/135022
2025-01-03bootstrap: support `./x check run-make-support`许杰友 Jieyou Xu (Joe)-0/+6
2025-01-03add coverage for multiple pathsonur-ozkan-0/+20
Signed-off-by: onur-ozkan <work@onurozkan.dev>
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-24 06:20:35 +0000