-
Notifications
You must be signed in to change notification settings - Fork 1
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
RFC: remove sycl chapter #4
Conversation
The topic was discussed in the WG. I talked 1-1 with Greg and Alexey and tried to incorporate their feedback. If no one objects within a week I will consider this proposal accepted and merge the PRs. |
proposals/001-removing-sycl.rst
Outdated
Recommendation | ||
Oneapi spec components should not use vendor extensions in interfaces. Either | ||
wrap the type (example above) or work with SYCL WG to make it part of SYCL | ||
spec or as a KHR extension. If there is a compelling reason to use a vendor |
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.
KHR is undefined at this point. I see it's defined as the identifier for supra-vendor organization extensions in https://registry.khronos.org/EGL/specs/eglspec.1.5.pdf. Will most readers be familiar with it through background with Khronos, or is a brief definition needed?
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 updated the explanation. @gmlueck: this was based on our conversation so please review
@akukanov
@gmlueck
See uxlfoundation/oneAPI-spec#530