[SYCL][CUDA][DOC] GettingStartedGuide.md to recommend cuda 11.6 #5917
Conversation
This file contains hidden or 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
bader
reviewed
Mar 29, 2022
bader
reviewed
Mar 29, 2022
pvchupin
reviewed
Mar 29, 2022
sycl/doc/GetStartedGuide.md
Outdated
| An installation of at least | ||
| [CUDA 11.0](https://developer.nvidia.com/cuda-11.0-download-archive) | ||
| is required for fully utilize Turing (SM 75) devices. | ||
| is required to fully utilize Turing (SM 75) devices and to enable Ampere (SM 80) | ||
| core features. | ||
|
|
||
| Currently, the only combination tested is Ubuntu 18.04 with CUDA 10.2 using |
There was a problem hiding this comment.
This looks a bit outdated. Let's remove first sentence?
There was a problem hiding this comment.
OK. I could just remove the sentence.
I know that DPC++ has been tested with SM61, SM70, SM71, SM80 using toolkit 11.0, 11.2, 11.3, 11.4, 11.6.
There was a problem hiding this comment.
There is another follow-up note.
The last sentence in this section looks outdated as well - "Windows CUDA support is experimental as it is not currently tested on the CI". We test CUDA backend on Windows platform in CI, but I don't know if it changes the status from "experimental".
There was a problem hiding this comment.
We think that the CUDA Windows support should be considered broadly speaking on the same level as the Linux support now that there is the Windows CI and tests are passing: I've gone ahead and removed the reference to experimental Windows support.
bader
reviewed
Mar 29, 2022
sycl/doc/GetStartedGuide.md
Outdated
| there is a known issue with some math builtins when using -O1/O2/O3 | ||
| Optimization options for CUDA toolkits prior to 11.6 (This is due to a bug in | ||
| earlier versions of the CUDA toolkit: see | ||
| [this issue](https://forums.developer.nvidia.com/t/libdevice-functions-causing-ptxas-segfault/193352). |
There was a problem hiding this comment.
Suggested change
| [this issue](https://forums.developer.nvidia.com/t/libdevice-functions-causing-ptxas-segfault/193352). | |
| [this issue](https://forums.developer.nvidia.com/t/libdevice-functions-causing-ptxas-segfault/193352)). |
bader
approved these changes
Mar 30, 2022
bader
changed the title
pvchupin
approved these changes
Mar 30, 2022
alexbatashev
added a commit
to alexbatashev/llvm
that referenced
this pull request
Apr 2, 2022
* sycl: (3343 commits) [SYCL][L0] Disable round-robin submissions to multiple CCSs (intel#5945) [SYCL][CUDA] Don't link pi_cuda against libsycl (intel#5908) [CI] Disable -Werror by default (intel#5889) [BuildBot] Uplift CPU/FPGAEMU RT version to 2022.13.3.0.16 (intel#5883) [SYCL][CUDA][libclc] Add support for atomic fp exchange and compare exchange (intel#5937) [SYCL] Fix device code outlining for static local variables (intel#5915) [SYCL][NFC] Refactor plugin CMakeLists.txt (intel#5799) [SPIR-V][Doc] Add JointMatrixWorkItemLengthINTEL instruction to joint matrix extension (intel#5781) [SYCL] Expand device_global map and make initialization order agnostic (intel#5902) [SYCL][CUDA] Add IPSCCP pass to O0 by default (intel#5900) [ESIMD] Disable ABI changes warnings in host compiler. (intel#5931) [SYCL] Make properties constructor constexpr (intel#5928) [NFC][SYCL] Fix static analysis warning (intel#5933) [CODEOWNERS][NFC] Assign code owners for CI scripts (intel#5873) [SYCL] Store the kernel object size in the integration header (intel#5862) [SYCL][ESIMD] Change esimd-verifier logic for detecting valid SYCL calls (intel#5914) [SYCL][CUDA][DOC] GettingStartedGuide.md to recommend cuda 11.6 (intel#5917) [SYCL][L0] Move command list cache usage under mutex (intel#5874) [SYCL][FPGA] Prepare future implementation of experimental pipe properties (intel#5886) [CI] Roll back intel driver to the latest version (intel#5925) ...
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.
An issue with CUDA toolkit versions prior to 11.6 has been identified: #5648 #4436
We now recommend that users install CUDA toolkit 11.6 and later for use with DPC++.
Note that the following line
"Currently, the only combination tested is Ubuntu 18.04 with CUDA 10.2 using
a Titan RTX GPU (SM 71)."
could also potentially be updated here. I just want to check that the semantics of this sentence is not meant to mean that this is the only combination that is consistently tested via the CI?