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
VC-WIN64-ARM build fails in VS 2019 (OpenSSL 3.0.8) #20234
Comments
|
This intrinsic only appears to be defined for x86/64 and shouldn't be used for ARM, AARCH64 or x86. |
|
Thanks for the fix. |
Would it be possible to publish when this will be released, even approximately? |
In an official release? There is no date set for the next release, even approximately. The VC-WIN64-ARM is an unadopted platform which means any regressions in it won't trigger a release. |
So, OpenSSL isn't officially supported on Windows arm64? MsQuic has been building/using it there with no issues until now. We're currently blocked on consuming the latest release because of this build break. |
|
The project's platform policy is clear: unadopted does not mean unsupported. It does mean that the project will have problems testing and fixing issues with the platform and that such fixes might take longer than they otherwise would. Consider volunteering as a community maintainer for the platform if it really is a blocker. |
I can personally vouch for this. There is a lot of satisfaction that comes from helping a community that would otherwise not get to benefit from OpenSSL. |
|
I can report that this problem exists in openssl 1.1.1t and the fix helps indeed there. We currently build openssl for 13 platforms including various combinations of 32/64bit, Intel/ARM and Linux/Windows/iOS/MacOS combinations. |
|
Understood. Thanks for the clarification and suggestions. |
openssl/openssl#20234 are fixed and released
|
This was fixed by #20244. Closing. |
The target VC-WIN64-ARM fails to build on VS2019. Previously built fine for 3.0.7 but the newly released 3.0.8 does not successfully build. The linker is complaining about
_umul128, which appears to be an Intel x64-specific intrinsic.This commit appears to be responsible:
b1892d2
x86 and x64 builds work fine in their respective build environments.
The text was updated successfully, but these errors were encountered: