-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 8 pull requests #107328
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 8 pull requests #107328
Conversation
The optimization that removes artifacts when building libraries is correct from the compiler's perspective but not from a debugger's perspective. Unpacked split debuginfo is referred to by filename and debuggers need the artifact that contains debuginfo to continue to exist at that path. Ironically the test expects the correct behavior but it was not running.
Putting the cfged functions into a seperate module and giving them better names.
…, r=davidtwco Preserve split DWARF files when building archives. r? ```@davidtwco```
Handle diagnostics customization on the fluent side (for one specific diagnostic) r? ```@davidtwco```
Migrate mir_build's borrow conflicts This also changes the error message slightly, for two reasons: - I'm not a fan of saying "value borrowed, by `x`, here" - it simplifies the error implementation significantly.
…=cjgillot `ty::tls` cleanups Pull it out into a separate file, make the conditional compilation more obvious and give the internal functions better names. Pulled out of rust-lang#106311 r? cjgillot
…orest,can-we-know-it-wasnt-revealed, r=oli-obk Use a type-alias-impl-trait in `ObligationForest`
Encode info for Adt in a single place. Split from rust-lang#98867
Custom mir: Add support for some remaining, easy to support constructs Some documentation for previous changes and support for `Deinit`, checked binops, len, and array repetition r? ```@oli-obk``` or ```@tmiasko```
Disable ConstGoto opt in cleanup blocks Fixes rust-lang#107315 . There is probably a smaller hammer that we could use here, but none that is super obviously correct. We can always revisit this in the future. Could not add a test because custom mir does not support cleanup blocks. However, did check that the fallible_iterator crate no longer ICEs with the other PR cherry picked. r? `@tmiasko`
@bors r+ rollup=never p=8 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 3e97763872 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (c62665e): 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.
|
Successful merges:
ty::tls
cleanups #107150 (ty::tls
cleanups)ObligationForest
#107168 (Use a type-alias-impl-trait inObligationForest
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup