-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 6 pull requests #112080
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 6 pull requests #112080
Conversation
All other instructions assume that user works with separate repository than Rust compiler repository. When one follows default instructions, cranelift codegen tries to use different sys-root and compiler internal crates which leads to compiler errors when building it. I needed to do all this steps while adding new intrinsic to rustc.
Move tests r? `@petrochenkov`
…anelift, r=bjorn3 Add build instructions for cranelift backend as part of Rust repo All other instructions assume that user works with separate repository than Rust compiler repository. When one follows default instructions, cranelift codegen tries to use different sys-root and compiler internal crates which leads to compiler errors when building it. I needed to do all this steps while adding new intrinsic to rustc. r? bjorn3
…compiler-errors Make `TyKind: Debug` have less verbose output Current `TyKind: Debug` impl is basically unusable for debugging, its too verbose even for verbose debugging 🤣 This PR replaces the debug logic for `TyKind` with a more manual debug impl instead of a hand expanded derived impl. This should help make rust-lang#107084 more reasonable to land since the output of `Ty: Debug` will be better. This isn't a fully completed change to the `Debug` impl of `TyKind` as there's still logic from the derive macro for some variants. Some of the variants are also not consisten with the `-Zverbose` printing of `Ty`, ideally `-Zverbose` printing of `Ty` would also just defer to the debug impl instead of having lots of checks in pretty printing. I plan on fixing this in follow up PRs since it seems tricky to do in this one and its already a large PR 😅
…p, r=lcnr Check nested obligations during coercion unify in new solver Found when triaging failing opaque tests with new solver. r? `@lcnr`
…-errors Suggest correct `self_ty` Fixes rust-lang#112036
… r=cjgillot Add a test for issue 110457/incremental ICE with closures with the same span Closes rust-lang#110457 It's probably possible to minimize the test case more, considering that we now know the underlying reason for the ICE, but I didn't. r? `@cjgillot`
@bors r+ rollup=never p=7 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 498553fc04 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (d9a4d5e): comparison URL. Overall result: ❌ regressions - 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 643.081s -> 645.901s (0.44%) |
Successful merges:
TyKind: Debug
have less verbose output #111988 (MakeTyKind: Debug
have less verbose output)self_ty
#112057 (Suggest correctself_ty
)Failed merges:
ui/discrim
dir #112068 (Move tests fromui/discrim
dir)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup