Skip to content

[ESIMD] Fix specialization/instantiation order in traits infra. #6677

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
Aug 31, 2022

Conversation

kbobrovs
Copy link
Contributor

This allows to avoid errors on Linux, where compiler picks up
instatiation of wrong specialization of elem_type_traits (the default
unusable one) when instatiating __raw_t alias.

Also do not use specialization of elem_type_traits (e.g. __raw_t) when
definition of the trait is not complete.

Make WrapperElementTypeProxy specific to sycl::half trait, because it
won't be needed for other types traits.

This allows to avoid errors on Linux, where compiler picks up
instatiation of wrong specialization of elem_type_traits (the default
unusable one) when instatiating __raw_t alias.

Also do not use specialization of elem_type_traits (e.g. __raw_t) when
definition of the trait is not complete.

Make WrapperElementTypeProxy specific to sycl::half trait, because it
won't be needed for other types traits.
@kbobrovs kbobrovs requested a review from a team as a code owner August 31, 2022 06:25
@kbobrovs kbobrovs requested review from v-klochkov and fineg74 August 31, 2022 06:25
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.

2 participants