-
Notifications
You must be signed in to change notification settings - Fork 356
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
can't call foreign function: InitOnceBeginInitialize when running on Windows #2595
Comments
Yes indeed, rust-lang/rust#102655 started using those functions so the i686-pc-windows-msvc target is currently defunct. x86_64-pc-windows-msvc should work though, so if you add EDIT: ah, I misread. You said the 64bit GNU target is broken, but the 64bit MSVC target works. That agrees with my observations. |
It depends on if the platform natively supports static Thread Local Storage (TLS). If not then this fallback code is used which includes these new functions. All windows-gnu targets have their own emulated TLS which does not play well with static TLS so the fallback is used. Static TLS should work on all msvc targets but for mysterious reasons it causes crashes on x86 so it's currently disabled there, |
use Scalar return types for Windows shims I started doing this while working on #2595; now I don't need the rest of this patch but this part still makes sense.
use Scalar return types for Windows shims I started doing this while working on rust-lang/miri#2595; now I don't need the rest of this patch but this part still makes sense.
My crate
aligners
got a failure in a scheduled Miri pipeline (job) absent any changes to the crate's code on the nightly version available in the night between 13th and 14th of October.Three of the pipeline targets seem to be failing:
Surprisingly, x86_64-pc-windows-msvc seems to be working.
Here's the full error:
There's none of my code in this trace. The tests failing are here, but they don't seem to be even running when this fails. Rerunning the actions causes the same result, so it doesn't look like a transient error.
The text was updated successfully, but these errors were encountered: