-
Notifications
You must be signed in to change notification settings - Fork 13k
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
regression: error[E0570]: "stdcall"
/"fastcall"
is not a supported ABI for the current target
#134712
Comments
This regressed in #129935. This crater run may have missed some crates due to a recently discovered regression in crater which was reporting a large number of "unknown" results (https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/crater.20returning.20unknown). cc @RalfJung. I assume the decision shouldn't really change (I still think we should make this FCW a hard error), but perhaps we should announce to more people that their crates are gonna break. |
Looking at the crates.io regressions, the only new ones are
So no action necessary here. I don't usually file issues for things not on crates.io; many of those are one-off experiments and the code is clearly not meant for wider consumption. |
just thinking if you want to add something in the release notes as a "FIY" in the compat notes (that's also an option) |
This should of course be listed in the compatibility notes, but I assume that is already planned anyway (#131039). |
I'd guess most of the real world failures will be on Windows. Having |
There's no behavior change on Windows. Only targets that are neither Windows nor 32bit-x86 are affected by this. |
Closing as won't fix in favor of existing relnotes item. |
and presumably related:
Version it worked on
It most recently worked on: 1.83.0
Version with regression
Using rustc 1.84.0-beta.4 in crater #134138.
@rustbot modify labels: +regression-from-stable-to-beta -regression-untriaged
The text was updated successfully, but these errors were encountered: