about summary refs log tree commit diff
path: root/src/bootstrap/config
AgeCommit message (Collapse)AuthorLines
2023-10-17improve bootstrap tests structureonur-ozkan-219/+0
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-14add unit test for Config::verifyonur-ozkan-1/+22
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-02Auto merge of #115898 - onur-ozkan:config-change-tracking, r=Mark-Simulacrumbors-6/+6
bootstrap major change detection implementation The use of `changelog-seen` and `bootstrap/CHANGELOG.md` has not been functional in any way for many years. We often do major/breaking changes but never update the changelog file or the `changelog-seen`. This is an alternative method for tracking major or breaking changes and informing developers when such changes occur. Example output when bootstrap detects a major change: ![image](https://github.com/rust-lang/rust/assets/39852038/ee802dfa-a02b-488b-a433-f853ce079b8a)
2023-10-01implement major change tracking for the bootstrap configurationonur-ozkan-6/+6
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-09-17micro-level optimizations for bootstraponur-ozkan-7/+7
Overall optimizations for bootstrap on conditions, assertions, trait implementations, etc. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-08-27replace outdated github username 'ozkanonur'ozkanonur-1/+1
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-07-09Use String or Int to set the opt levelhi-rustin-1/+4
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
2023-07-02Fix broken testshi-rustin-5/+1
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
2023-07-01Add tests for RustOptimizehi-rustin-0/+19
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
2023-06-26bootstrap: rename 'user' profile to 'dist'clubby789-0/+19
2023-05-19Override config.toml options from command lineclubby789-6/+71
2023-05-06Migrate bootstrap to Clap-based argumentsclubby789-1/+7
2023-04-06Auto merge of #109162 - ozkanonur:extend_detect_src_and_out_test, r=jyn514bors-21/+44
extend `detect_src_and_out` test > I was thinking about the following cases when I wrote the comment in #109055 > > 1. Running bootstrap from the source root. > 2. Running from a subdirectory of the source root. > 3. Running from outside the source root. > 4. Running on a different machine from where bootstrap was compiled (which will be important > for #107812). You can mostly replicate this by renaming the source root so it no longer exists on disk. > 5. Running with `--build-dir`. > 6. Running with `$RUST_BOOTSTRAP_CONFIG` set in the environment and `build-dir` set in the file. Tested all the topics mentioned above. All worked fine. The test is now also covers if build dir is manually specified in config. r? `@jyn514` helps #109120 partially
2023-04-06improve/extend `detect_src_and_out` testozkanonur-21/+44
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-03-24Rename 'src/bootstrap/native.rs' to llvm.rsRobin Hafid-1/+1
Renamed 'native.rs' to 'llvm.rs', also moved `TestHelpers` to `test.rs`.Replaced all the `native.rs` ocurrences at `src/bootstrap` files to `llvm.rs`
2023-03-12create `config::tests::detect_src_and_out` test for bootstrapozkanonur-2/+33
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-02-28Skip test `download_ci_llvm` with modified LLVMJosh Stone-0/+5
2023-01-27Revisit fix_is_ci_llvm_available logic; read build triple from tomlSergey Prytkov-0/+7
2022-11-19Set `download-ci-llvm = "if-available"` by default when `channel = "dev"`Joshua Nelson-0/+24
See https://github.com/rust-lang/compiler-team/issues/566. The motivation for changing the default is to avoid downloading and building LLVM when someone runs `x build` before running `x setup`. The motivation for only doing it on `channel = "dev"` is to avoid breaking distros or users installing from source. It works because `dev` is also the default channel. The diff looks larger than it is; most of it is moving the `llvm` branch below the `rust` so `config.channel` is set.