Minimal fix for Windows AVX512 intrinsics issue #574
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6eb1fcc to
342276f
Compare
- Bump setup-ruby-and-rust action to latest commit - Add AVX512/FP16 workaround for Windows x86_64 in bindgen - Disable layout/debug derives for Ruby 2.7/3.0 on MinGW - Opaque __mingw_ldbl_type_t to avoid ABI issues
342276f to
bfc7eda
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides a minimal fix for the Windows build failures caused by Clang 20's AVX512 FP16 intrinsics.
The fix simply targets basic x86-64 without vector extensions on Windows x86_64 systems by adding:
-march=x86-64-mtune=genericThis prevents Clang from loading the problematic AVX512 intrinsics headers that contain types like
__m512hwhich bindgen cannot handle.