-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 9 pull requests #100123
Rollup of 9 pull requests #100123
Conversation
This reduces the compiler-doc file from 40K to 36K, a 10% reduction in size.
Set llvm configs when building lld Several LLVM configs applied when building LLVM should also be applied when building LLD. For example, without the fix, setting both `llvm.thin-lto=true` and `rust.lld=true` when building on Linux will fail, since we need to manually override the compiler and linker to `clang`, but those will not be used when building LLD, causing link errors. r? ```@jyn514```
Fix backwards-compatibility check for tests with `+whole-archive` Fixes rust-lang#100066
…s, r=GuillaumeGomez rustdoc: use a more compact encoding for source-files.js This reduces the compiler-doc file from 40K to 36K, a 10% reduction in size.
…Dylan-DPC Fix typo r? ```@jackh726```
…ylan-DPC Remove more Clean trait implementations Follow-up of rust-lang#99638. r? ``@notriddle``
…871, r=compiler-errors Add regression test for rust-lang#90871 closes rust-lang#90871
fix trailing whitespace in error message
…rrors Provide suggestion on missing `let` in binding statement Fix rust-lang#78907. Fallout from the type ascription syntax.
FilesTimes support does not build for ESP-IDF Commit rust-lang@1f5d8d4 broke STD for `target_os = "espidf"`. In future, we might come up with something more sophisticated (as in using the `utime` function which *is* available on the ESP-IDF platform), but for now we are treating ESP-IDF just like `Redox` in that the new API fails at runtime. Most important for us ATM is to restore successful compilation of STD on our platform.
@bors r+ rollup=never p=9 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (1ad5635): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Successful merges:
+whole-archive
#100068 (Fix backwards-compatibility check for tests with+whole-archive
)let
in binding statement #100111 (Provide suggestion on missinglet
in binding statement)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup