Skip to content

Conversation

@Fznamznon
Copy link
Contributor

Earlier a mechanism to lift SYCL device code restrictions in C++ manifestly constant-evaluated expressions was implemented in the front-end. It was enabled under an option since it wasn't specified. Since then it has been decided to make this behavior default for SYCL 2020. This PR removes the option that was enabling the new behavior and enables it by default.

…contexts

Earlier a mechanism to lift SYCL device code restrictions in C++
manifestly constant-evaluated expressions was implemented in the front-end.
It was enabled under an option since it wasn't specified.
Since then it has been decided to make this behavior default for SYCL 2020.
This PR removes the option that was enabling the new behavior and
enables it by default.
@Fznamznon Fznamznon requested a review from gmlueck October 2, 2024 13:09
@Fznamznon Fznamznon requested review from a team as code owners October 2, 2024 13:09
Copy link
Contributor

@gmlueck gmlueck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we want this to be the default behavior, not tied to a special option. The matching PR to the SYCL specification is KhronosGroup/SYCL-Docs#388.

Copy link
Contributor

@keryell keryell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

@Fznamznon
Copy link
Contributor Author

@intel/llvm-gatekeepers , could you please merge? This is ready

@sommerlukas sommerlukas merged commit 10fee97 into intel:sycl Oct 4, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants