-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Disable alignment checks on i686-pc-windows-msvc #112684
Conversation
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
Thanks for the tweak. I was thinking it would be good to cite something but I wasn't sure where. |
You're welcome. Thanks for the quick turn around on this! @bors r+ rollup |
… r=wesleywiser Disable alignment checks on i686-pc-windows-msvc r? `@wesleywiser` Because you were in the Zulip discussion of this: https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202023-06-15 cc rust-lang#112480
@@ -14,6 +14,10 @@ pub struct CheckAlignment; | |||
|
|||
impl<'tcx> MirPass<'tcx> for CheckAlignment { | |||
fn is_enabled(&self, sess: &Session) -> bool { | |||
// FIXME(#112480) MSVC and rustc disagree on minimum stack alignment on x86 Windows | |||
if sess.target.llvm_target == "i686-pc-windows-msvc" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this potentially going to make some of the MIR tests for this fail on i686-msvc? Are there any tests that should get something like a ignore-i686-pc-windows-msvc
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think just the test for the alignment check itself. The mir-opt tests have debug assertions disabled and I think I was otherwise pretty careful to modify the other tests so that they are not perturbed by them, but that was some time ago.
I'd prefer to be able to run the msvc test suite locally but I don't think that's supported on a Linux host?
@bors r- failed in rollup: #112689 (comment) |
55d680b
to
0a445af
Compare
0a445af
to
c54672e
Compare
@bors r=wesleywiser |
@bors r+ |
…mpiler-errors Rollup of 7 pull requests Successful merges: - rust-lang#111074 (Relax implicit `T: Sized` bounds on `BufReader<T>`, `BufWriter<T>` and `LineWriter<T>`) - rust-lang#112226 (std: available_parallelism using native netbsd api first) - rust-lang#112474 (Support 128-bit enum variant in debuginfo codegen) - rust-lang#112662 (`#[lang_item]` for `core::ptr::Unique`) - rust-lang#112665 (Make assumption functions in new solver take `Binder<'tcx, Clause<'tcx>>`) - rust-lang#112684 (Disable alignment checks on i686-pc-windows-msvc) - rust-lang#112706 (Add `SyntaxContext::is_root`) r? `@ghost` `@rustbot` modify labels: rollup
…k-Simulacrum [beta] backport This PR backports: - rust-lang#112684: Disable alignment checks on i686-pc-windows-msvc - rust-lang#112581: [rustdoc] Fix URL encoding of % sign - rust-lang#112312: Update to LLVM 16.0.5 - rust-lang#112266: Fix type-inference regression in rust-lang#112225 - rust-lang#112062: Make struct layout not depend on unsizeable tail r? `@Mark-Simulacrum`
I don't understand why the tags here indicate a stable backport? #98112 is on the 1.70 train, this here landed for the 1.71 train, so a beta backport should be sufficient. |
Because if there were a 1.70.1 release then it would be worth including it. |
Oh, when I said this landed on the 1.71 train I was wrong -- the milestone in this PR got changed and no longer reflects the train it originally landed in. That lead me down the wrong trail. This landed in the 1.72 train. |
r? @wesleywiser Because you were in the Zulip discussion of this: https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202023-06-15
cc #112480