This commit turns "Actual" into "Expected" for the following problem:
Steps:
1. Do some quick and experimental local code changes in the compiler code.
2. Run `./x build`.
3. Observe `error: warnings are denied by `build.warnings` configuration`.
4. Decide to not care and want to allow warnings.
5. Search for `build.warnings` in **bootstrap.example.toml**
Actual:
No hits. You get frustrated because didn't learn how to allow warnings.
Expected:
You get a hit and can easily see how to allow warnings.
Do not enable split debuginfo for windows-gnu
Because rustc doesn't handle split debuginfo for these targets, enabling that option causes them to be missing some of the debuginfo.
This makes easy to persistently pass any flag to the compiler when
building rustc.
For example you can use a different linker by putting the following in
`bootstrap.toml`:
```toml
[rust]
rustflags = ["-Clinker=clang", "-Clink-arg=--ld-path=wild"]
```
Build rustc and tools with -Zannotate-moves by default. Adds toml config
options to set the annotation size limit.
This has no measurable effect on output binary size or compile time.
It is now required to provide a resource compiler on windows when
compiling rust. This allows toolchain builders to explicitly provide a
path to an alternative, such as llvm-rc, instead of the one that's
provided by the Windows SDK.
Create a dedicated enum to abstract the different ways compiler-builtins
can be configured.
This also relaxes build.optimized-compiler-builtins to accept the path
of a library to match the behavior of <target>.optimized-compiler-builtins
override.
Extend the <target>.optimized-compiler-builtins bootstrap option to accept a
path to a prebuilt compiler-rt builtins library, and update compiler-builtins
to enable optimized builtins without building compiler-rt builtins.
Fix typos in bootstrap.example.toml
Founds these small typos while looking around.
`equivelent` -> `equivalent`
`recommeded` -> `recommended`
cheers :)
prefixing each key with its section means you don't
need to scroll up 4 pages to see which section
a particular key is from.
target specific options were kept in old format
since the exact section name depends on the target,
so those options must now be moved to the bottom of
the file.
Download GCC from CI on test builders
This should reduce the duration of the `x86_64-gnu-llvm-18` job, which runs on PR CI, which is currently the only one that builds GCC (outside of the x64 dist builder).
Since we handle the GCC download in the GCC step, and not eagerly in config, we can set this flag globally across all test builders, as it won't do anything unless they actually try to build GCC.
Opening as a draft to test if it works on CI, because I still need to implement logic to avoid the download if there are any local modifications to GCC (essentially the "if-unchanged" mode, although I want to try something a bit different).
r? ```@ghost```
Martin Nordholts