-
Notifications
You must be signed in to change notification settings - Fork 794
[SYCL][SPIRV BE] Disable SPV_KHR_float_controls2 extension. #20519
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
base: sycl
Are you sure you want to change the base?
[SYCL][SPIRV BE] Disable SPV_KHR_float_controls2 extension. #20519
Conversation
| // is growing. Let's postpone the decision on which extensions to enable until | ||
| // - the list is stable, and | ||
| // - we decide on a mapping of user requested extensions into backend's ones. | ||
| // Meanwhile we enable all the SPIR-V backend extensions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update the comment to reflect the change, perhaps embellish on support expectations now and moving forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can definitely add that we are enabling all except this particular one. For the rest, I'm doing it this way to unblock LLVM-SPIRV pulldown, but I'm working on preparing the actual list with extensions to be enabled, instead of all. I can update the comment on support expectations now and in the future, but I plan to remove this comment completely in my next patch, which hopefully will take no more than 1-2 weeks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great - thanks
SPV_KHR_float_controls2 is not supported yet by our driver, so we need to explicitly disable it for now.
SPV_KHR_float_controls2 is not supported yet by our driver, so we need to explicitly disable it for now.