-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Not planned
Parent:Crater runs for 1.84
Labels
C-bugCategory: This is a bug.Category: This is a bug.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
Milestone
Description
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/ChlorideCull.chcl_now_playing/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/PocketRelay.me3-offline-plugin/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/Sgeo.rwg_to_rwx/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/plegat.RLaminateAnalysis/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/sergemalo.sm-checkers-engine/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/weslenng-labs.visual-basic-rs/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/reg/dx_core-0.3.0/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/reg/miniblink-0.3.0/log.txt
error[E0570]: `"stdcall"` is not a supported ABI for the current target
and presumably related:
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/reg/vtable_gen-1.1.0/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.84.0-4-retry2/beta-2024-12-08/gh/MrElectrify.vtable_gen/log.txt
error[E0570]: `"fastcall"` is not a supported ABI for the current target
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
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
Type
Projects
Relationships
Parent issue
Development
Select code repository
Activity
compiler-errors commentedon Dec 23, 2024
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.
cuviper commentedon Dec 24, 2024
If you're looking for people to notify, a few more showed up in the rustdoc run:
(edit: appended 3 more that crater hadn't IDed as E0570)
RalfJung commentedon Dec 24, 2024
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.
apiraino commentedon Dec 26, 2024
just thinking if you want to add something in the release notes as a "FIY" in the compat notes (that's also an option)
RalfJung commentedon Dec 26, 2024
This should of course be listed in the compatibility notes, but I assume that is already planned anyway (#131039).
ChrisDenton commentedon Dec 26, 2024
I'd guess most of the real world failures will be on Windows. Having
stdcall
andfastcall
meanC
on x64 is the C/C++ behaviour.RalfJung commentedon Dec 26, 2024
There's no behavior change on Windows. Only targets that are neither Windows nor 32bit-x86 are affected by this.
Mark-Simulacrum commentedon Jan 3, 2025
Closing as won't fix in favor of existing relnotes item.