-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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 #106025
Rollup of 6 pull requests #106025
Conversation
When building with Fat LTO and BTI enabled on aarch64, the BTI is set to `Module::Min` for alloc shim but is set to `Module::Error` for the crate. This was fine when we were using LLVM-14 but LLVM-15 changes it's behaviour to support for compiling with different `mbranch-protection` flags. Refer: rust-lang/llvm-project@b0343a3
CI fails when building with LLVM-13. This raises unknown behavior constant `8` from IRVerifier.
This has a 10000000% chance of us causing a cycle if we're not careful
This was a regression from the reverted rust-lang#105250 which is now covered by a test.
…tebank Don't ICE in `check_must_not_suspend_ty` for mismatched tuple arity These expressions are just used for their spans, so make it best-effort here. Fixes rust-lang#105728
… r=nikic Correct branch-protection ModFlagBehavior for Aarch64 on LLVM-15 When building with Fat LTO and BTI enabled on aarch64, the BTI is set to `Module::Min` for alloc shim but is set to `Module::Error` for the crate. This was fine when we were using LLVM-14 but LLVM-15 changes it's behaviour to support for compiling with different `mbranch-protection` flags. Refer: rust-lang/llvm-project@b0343a3 fixes rust-lang#102162
Various cleanups This PR pulls changes out of rust-lang#101900 that can land on master immediately r? ``@fee1-dead``
…cks, r=estebank Method chain nitpicks Just fixing some little things I didn't see in review from that method chain PR. r? `@estebank`
…trochenkov Test that async blocks are `UnwindSafe` This was a regression from the reverted rust-lang#105250 which is now covered by a test.
Clarify that raw retags are not permitted in Mir Not sure when this changed, but documentation and the validator needed to be updated. This also removes raw retags from custom mir. cc rust-lang/miri#2735 r? `@RalfJung`
@bors r+ rollup=never p=6 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 8574880108 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (75f4ee8): 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)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#105837 (Don't ICE in `check_must_not_suspend_ty` for mismatched tuple arity) - rust-lang#105932 (Correct branch-protection ModFlagBehavior for Aarch64 on LLVM-15) - rust-lang#105960 (Various cleanups) - rust-lang#105985 (Method chain nitpicks) - rust-lang#105996 (Test that async blocks are `UnwindSafe`) - rust-lang#106012 (Clarify that raw retags are not permitted in Mir) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Successful merges:
check_must_not_suspend_ty
for mismatched tuple arity #105837 (Don't ICE incheck_must_not_suspend_ty
for mismatched tuple arity)UnwindSafe
#105996 (Test that async blocks areUnwindSafe
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup