-
Notifications
You must be signed in to change notification settings - Fork 171
NEO/Win10 performance regression from .6025 onward including today's .6194 #17
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 Allan, Thank you for making us aware of this potential regression. Please send your kernels to my email (listed in my profile) with a detailed description on how to reproduce. Our compiler team will take a look and see if we can reproduce this behavior and provide a fix. -Alex |
Thanks, sent! |
…s fixes issue #17 for IGC Change-Id: Iabb9b54945a44aeafd3836f250095b71a627185f
The commit attached (1451db9) removes the spills you were seeing post .6025. Please verify and close. |
Thanks, I will confirm as soon as the next compute runtime release appears. |
Hello Allan, |
Co-authored-by: Jacek Jankowski <[email protected]>
Co-authored-by: Jacek Jankowski <[email protected]>
Every NEO/Win10 driver post .6025 exhibits the same regression (huge spillage).
As noted here, .6025 works perfectly.
All kernels listed here are decorated with a reqd_subroup_size(8) and compiled with
ioc64
.Let me know who I can send the kernels to.
The text was updated successfully, but these errors were encountered: