-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[beta] backports #131423
[beta] backports #131423
Conversation
There are a couple more nominated backports as well, so I'll hold off a few days in case they're accepted... |
@cuviper the passing current cargo to run-make one (#130642) is kind of funny, because:
You previously said
So if #130642 isn't necessary, I would recommend not backporting it. |
Yeah, I agree we probably don't need #130642, and I forgot that I nominated it myself 😬 -- I'll drop that. |
@bors r+ rollup=never |
[beta] backports - Only add an automatic SONAME for Rust dylibs rust-lang#130960 - Reject leading unsafe in `cfg!(...)` and `--check-cfg` rust-lang#131057, resolving rust-lang#131055 - Disable jump threading `UnOp::Not` for non-bool rust-lang#131201 - Update LLVM submodule rust-lang#131448 r? ghost
[beta] backports - Only add an automatic SONAME for Rust dylibs rust-lang#130960 - Reject leading unsafe in `cfg!(...)` and `--check-cfg` rust-lang#131057, resolving rust-lang#131055 - Disable jump threading `UnOp::Not` for non-bool rust-lang#131201 - Update LLVM submodule rust-lang#131448 r? ghost
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors retry |
@bors p=1 |
[beta] backports - Only add an automatic SONAME for Rust dylibs rust-lang#130960 - Reject leading unsafe in `cfg!(...)` and `--check-cfg` rust-lang#131057, resolving rust-lang#131055 - Disable jump threading `UnOp::Not` for non-bool rust-lang#131201 - Update LLVM submodule rust-lang#131448 r? ghost
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Oh - do we not have the mitigations for the MSVC failure on the beta branch? @bors retry |
What's the mitigation? I should probably backport it too. |
I think currently we have #130151 and #130072 (cc @ChrisDenton) |
Thanks! I went ahead and backported them. |
@bors r+ |
☀️ Test successful - checks-actions |
cfg!(...)
and--check-cfg
Reject leading unsafe incfg!(...)
and--check-cfg
#131057, resolvingcfg!(unsafe(foo))
and--check-cfg=unsafe(cfg(foo))
are erroneously accepted on beta #131055UnOp::Not
for non-bool Disable jump threadingUnOp::Not
for non-bool #131201r? ghost