-
Notifications
You must be signed in to change notification settings - Fork 262
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
update list of fully implemented instruction sets #1152
Conversation
"SSE4.1 List including CRC32" - I think the CRC32 instructions are some of the "non-SIMD" SSE4.2, not SSE4.1. Related question is if SIMDe implements the non-SIMD instructions of MMX, SSE, SSE2, SSE3? From a cursory search I did it seems the answer is no. Also, would you like to have Issues raised for:
|
Good catch, I'll split out CRC32 separately since our SSE4.2 support is incomplete. And https://github.com/simd-everywhere/implementation-status/blob/main/x86.md#vpclmulqdq is implemented, so I'll add it to the list Happy to have new issues for AVX512-VAES, SSE4a, FMA4 and others, sure. Please double check https://github.com/simd-everywhere/implementation-status/blob/main/x86.md in case it is already done, but not documented. If you or your collaborators are interested in implementing some of these, we can have a video call where I can walk you through adding a new intrinsic implementation. |
OK, created a few Issues. Looking at implementation status/x86.md:
Readme file has a section about hardware architectures tested in CI, but in ci.yml I see more - should the following be specified in the README.md?
|
See https://github.com/simd-everywhere/simde?tab=readme-ov-file#caveats Please create issues or PRs for the others, thanks! |
Per simd-everywhere#1152 (comment) Should the following two architectures also be added? - ARMv8 SVE - it's in [simde-features.h](https://github.com/simd-everywhere/simde/blob/b88a66de3a7de7a16099ab28019bc566e4468b82/simde/simde-features.h), but I couldn't find it in ci.yml - z/Architecture *ZVECTOR* - it's in simde-features.h, but ci.yml just lists s390x, so unclear if ZVECTOR extensions are utilized
No description provided.