[SYCL][Doc][RTC] Document [un]supported features and build_options
#17459
+107
−13
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
Signed-off-by: Julian Oppermann <julian.oppermann@codeplay.com>
Pennycook
requested changes
Mar 14, 2025
sycl/doc/extensions/experimental/sycl_ext_oneapi_kernel_compiler.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/experimental/sycl_ext_oneapi_kernel_compiler.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/experimental/sycl_ext_oneapi_kernel_compiler.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/experimental/sycl_ext_oneapi_kernel_compiler.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/experimental/sycl_ext_oneapi_kernel_compiler.asciidoc
Outdated
Show resolved
Hide resolved
Comment on lines
+1032
to
+1033
| With the exception of the `-Xs` option, all other options to control | ||
| ahead-of-time (AOT) compilation, such as `-fsycl-targets`, are unsupported. |
There was a problem hiding this comment.
What does "unsupported" mean? Is this undefined behavior, or can this be diagnosed via a errc::build exception?
This question also applies to all instances of "unsupported" appearing below.
sycl/doc/extensions/experimental/sycl_ext_oneapi_kernel_compiler.asciidoc
Outdated
Show resolved
Hide resolved
Comment on lines
+1068
to
+1072
| The `kernel_compiler` implementation in {dpcpp} supports persistent caching. To | ||
| enable it, set the the environment variable `SYCL_CACHE_PERSISTENT=1`. The | ||
| location of the cache can be changed by setting `SYCL_CACHE_DIR`. Refer to | ||
| https://intel.github.io/llvm/design/KernelProgramCache.html#persistent-cache for | ||
| more details on how to control the cache. |
There was a problem hiding this comment.
Has this been reviewed somewhere else, perhaps as part of the design of the run-time compiler?
I'm a little surprised that JIT compilation of kernels embedded in the binary would use the same cache as explicit run-time compilation of kernels. I would have expected separate controls.
There was a problem hiding this comment.
The implementation PR is #16823 and has been approved by @cperkinsintel.
Signed-off-by: Julian Oppermann <julian.oppermann@codeplay.com>
Signed-off-by: Julian Oppermann <julian.oppermann@codeplay.com>
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.
Update the non-normative section in the
kernel_compilerextension to reflect what's currently supported in DPCPP.