Skip to content

[SYCL] Don't use C++17 CTAD causing post-commit failures #7635

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 1 commit into from
Dec 5, 2022

Conversation

againull
Copy link
Contributor

@againull againull commented Dec 5, 2022

@againull againull requested review from a team as code owners December 5, 2022 06:05
@romanovvlad
Copy link
Contributor

HIP failures are unrelated.

@romanovvlad romanovvlad merged commit c1947ff into intel:sycl Dec 5, 2022
@keryell
Copy link
Contributor

keryell commented Dec 8, 2022

I think I was the culprit for this CTAD suggestion... But SYCL 2020 requires C++17!

@aelovikov-intel
Copy link
Contributor

CTAD support is still imperfect in compilers we use. We have internal testing with "-fsycl-use-host-compiler=cl" (MSVC) that results in CTAD-related issues for sycl::accessor, unless /std:c++latest is used (and fails in /std:c++17 mode).

@keryell
Copy link
Contributor

keryell commented Dec 8, 2022

Ok, I guess this is a bug in MacOS Xcode 14 and their C++ library. :-(

@againull againull deleted the remove_ctad branch December 13, 2022 20:34
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