-
Notifications
You must be signed in to change notification settings - Fork 171
Add way to control SIMD width #15
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
Comments
Hello Axel, For forcing SIMD-8 please use the following attribute.... This works on any of the three SIMD sizes. |
It works indeed, thank you ! |
VPG-SWE-Github
pushed a commit
that referenced
this issue
Nov 2, 2020
Co-authored-by: Jacek Jankowski <[email protected]>
VPG-SWE-Github
pushed a commit
that referenced
this issue
Nov 3, 2020
Co-authored-by: Jacek Jankowski <[email protected]>
VPG-SWE-Github
pushed a commit
that referenced
this issue
Nov 3, 2020
VPG-SWE-Github
pushed a commit
that referenced
this issue
Nov 3, 2020
VPG-SWE-Github
pushed a commit
that referenced
this issue
Nov 3, 2020
VPG-SWE-Github
pushed a commit
that referenced
this issue
Nov 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some reasons, a few changes in my kernels can lead the compiler to pick a different choice for SIMD width (8, 16 or 32).
For some reason I don't explain, some of my kernels using shared memory and barriers perform very significantly better (several times faster) when the selected SIMD width is 8.
Thus I'd like a way to enforce the choice of SIMD width of 8. (Also ideally compiler would make better choices).
Maybe make
__attribute__((vec_type_hint(float8)))
trigger SIMD-8 for example ?The text was updated successfully, but these errors were encountered: