-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 5 pull requests #118001
Rollup of 5 pull requests #118001
Conversation
We unconditionally set this to avoid recompiling tools between `x check $tool` and `x test $tool` executions. See rust-lang#116538 for more information. Signed-off-by: onur-ozkan <work@onurozkan.dev>
This was made possible by the removal of plugin support, which simplified lint store creation. This simplifies the places in rustc and rustdoc that call `describe_lints`, which are early on. The lint store is now built before those places, so they don't have to create their own lint store for temporary use, they can just use the main one.
Lint registration now happens early enough that we can run it from `Config`, before `Compiler` is created.
Move `lint_store` Some nice cleanups enabled by the removal of compiler plugins. r? `@cjgillot`
…lacrum bootstrap: simplify setting unstable-options for tools Previously, we unconditionally(instead of `if path == "src/tools/clippy" || ..`) set this (to prevent recompiling tools between `x check $tool` and '` check $another_tool` executions) specifically for tools in the `x check` step. This PR relocates that logic to `fn prepare_tool_cargo`, making it step-agnostic. Fixes rust-lang#116538 Fixes rust-lang#117983
docs(release): Clarify cargo entries Trying to make these easier to scan and more understandable out of the context of their PR
…-Simulacrum avoid exhaustive i16 test in Miri rust-lang#116301 added a test that is way too slow to be running in Miri. So let's only test a few hopefully representative cases.
…compiler-errors `rustc_query_system` cleanups Minor cleanups. r? `@compiler-errors`
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 15a791fa35 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (4770d91): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 674.777s -> 676.51s (0.26%) |
Note for next week's triage if this PR comes up in the results: the |
Successful merges:
lint_store
#117649 (Movelint_store
)rustc_query_system
cleanups #117963 (rustc_query_system
cleanups)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup