SYCL Compiler Support, main branch (2024.11.05.)#301
Merged
krasznaa merged 3 commits intoacts-project:mainfrom Nov 7, 2024
Merged
SYCL Compiler Support, main branch (2024.11.05.)#301krasznaa merged 3 commits intoacts-project:mainfrom
krasznaa merged 3 commits intoacts-project:mainfrom
Conversation
As oneAPI 2025.0.0 treats that as the canonical include, giving warnings about using <CL/sycl.hpp>.
501c693 to
9df45ce
Compare
paulgessinger
approved these changes
Nov 7, 2024
Member
paulgessinger
left a comment
There was a problem hiding this comment.
Looks good, as far as I can tell.
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
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.
Triggered by the release of oneAPI 2025.0.0, which deprecates the
<CL/sycl.hpp>include, I set out to make sure that the project would work with both oneAPI 2025.0.0 and AdaptiveCpp 24.06.0.I had to do the following:
<CL/sycl.hpp>includes with<sycl/sycl.hpp>;cl::sycl::namespace with::sycl::;--acpp-version) for collecting the necessary info;vecmem::device_atomic_reffunction calls with the type that the atomic reference is created on top of;-fsanitize=undefinedwhen targeting offload backends AdaptiveCpp/AdaptiveCpp#1283, it's a different issue after all. But the ability to turn off the usage of UBSAN on our end is still necessary.<sycl/sycl.hpp>would be included "early enough" in one of our tests, otherwisedevice_atomic_ref.hppwould select the wrong backend. Which I'm very surprised didn't hit us with oneAPI... 😕With all of this in place, the code works relatively well like the following for instance:
The OpenMP backed tests don't all succeed, but that's something to worry about later... 🤔