Skip to content

[SYCL] Fix instantiation after specialization warning #2818

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 1, 2020

Conversation

alexbatashev
Copy link
Contributor

Explicit instantiation of template that occurs after an explicit specialization
has no effect. Move template specializations to header to avoid this kind
of warnings.

Explicit instantiation of template that occurs after an explicit specialization
has no effect. Move template specializations to header to avoid this kind
of warnings.
@alexbatashev alexbatashev requested a review from a team as a code owner November 25, 2020 08:06
Copy link
Contributor

@smaslov-intel smaslov-intel left a comment

Choose a reason for hiding this comment

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

Don't you want to add a test?

@alexbatashev
Copy link
Contributor Author

Don't you want to add a test?

Tests won't help here. I intend to enable this warning for SYCL target (it seems to be supported by our GCC versions), but that's the job for a different PR.

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.

3 participants