Skip to content

[SYCL] Fix sycl::vec constructor ambiguity #8608

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 21, 2023

Conversation

steffenlarsen
Copy link
Contributor

Recent changes to the sycl::vec class added a private constructor taking and array. This resulted in constructor ambiguity when passing an initializer list, despite the constructor being private. This commit removes the constructor, making the implementation use the constructor taking both an array and an index sequence directly.

Recent changes to the sycl::vec class added a private constructor taking
and array. This resulted in constructor ambiguity when passing an
initializer list, despite the constructor being private. This commit
removes the constructor, making the implementation use the constructor
taking both an array and an index sequence directly.

Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com>
@steffenlarsen steffenlarsen requested a review from a team as a code owner March 10, 2023 10:26
Co-authored-by: Alexey Sachkov <alexey.sachkov@intel.com>
@steffenlarsen steffenlarsen temporarily deployed to aws March 10, 2023 11:16 — with GitHub Actions Inactive
@steffenlarsen steffenlarsen temporarily deployed to aws March 10, 2023 12:16 — with GitHub Actions Inactive
@AlexeySachkov
Copy link
Contributor

@KseniyaTikhomirova, @intel/llvm-reviewers-runtime, could you please take a look?

@AlexeySachkov AlexeySachkov requested a review from a team March 16, 2023 09:19
Copy link
Contributor

@bso-intel bso-intel left a comment

Choose a reason for hiding this comment

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

LGTM

@againull againull merged commit 12a4566 into intel:sycl Mar 21, 2023
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.

5 participants