Add framework for unified spec #616
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add a section to the introduction explaining that this document is a specification for SYCL 2020 and SYCL-Next and also for the KHR extensions. * Add a (mostly empty) appendix that will hold the future KHR extensions. * Change some references to "SYCL 2020" to more general wording, since they apply also to SYCL-Next. * Remove references to "SYCL Next" and use the Asciidoc `SYCL_VERSION` attribute instead.
It seems confusing to have an appendix with no KHR extensions. I think we will have at least one by the time this spec is published, but just to be safe add a sentence stating that there are no KHR extensions yet in the appendix. We'll remove this sentence when we have our first KHR.
|
Merging as the WG already approved this change when it was an internal MR. |
keryell
pushed a commit
that referenced
this pull request
Sep 10, 2024
Add framework for unified spec
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a section to the introduction explaining that this document is a
specification for SYCL 2020 and SYCL-Next and also for the KHR
extensions.
Add a (mostly empty) appendix that will hold the future KHR
extensions.
Change some references to "SYCL 2020" to more general wording, since
they apply also to SYCL-Next.
Remove references to "SYCL Next" and use the Asciidoc SYCL_VERSION
attribute instead.
This corresponds to internal MR 755