Skip to content
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

Use AVX if available #3019

Open
eggrobin opened this issue May 31, 2021 · 1 comment
Open

Use AVX if available #3019

eggrobin opened this issue May 31, 2021 · 1 comment

Comments

@eggrobin
Copy link
Member

eggrobin commented May 31, 2021

Because of different alignment requirements and VEX encoding/VZEROUPPER woes, and because it would be so low-level and pervasive (we cannot gate every operation on R3Element behind a CPUID test) we need a separate DLL for that, with an intermediate layer that chooses which one to use based on CPUID.

We could generate the intermediate layer from journal.proto, and LoadLibrary/GetProcAddress etc.

This blocks FMA usage on Linux & macOS, see #3010 (comment).

@Growflavor
Copy link

Growflavor commented Sep 11, 2021

just curious: is this relevant only for Linux & macOS? Or is there something here that might also be useful as an alternative to FMA3 on Windows 10 machines with older chips? For users like me who are stuck (for a few more years) with Ivy-Bridge processors that support AVX but not FMA3/AVX2:
IvyBridge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants