Skip to content

Conversation

aelovikov-intel
Copy link
Contributor

Those looked wrong but I don't have any tests. We can either merge as-is or create an issue for the original author(s) to follow up.

Seems that bfloat16 APIs don't need any changes since C++23's std::bfloat16 behaves in a similar way (although it's fundamental instead of a class type).

Those looked wrong but I don't have any tests. We can either merge as-is
or create an issue for the original author(s) to follow up.

Seems that `bfloat16` APIs don't need any changes since C++23's
`std::bfloat16` behaves in a similar way (although it's fundamental
instead of a class type).
Copy link
Contributor

@steffenlarsen steffenlarsen left a comment

Choose a reason for hiding this comment

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

Great find! We should really extend out testing of this...

Copy link
Contributor

@intel/llvm-gatekeepers please consider merging

@steffenlarsen steffenlarsen merged commit b57a01a into intel:sycl Sep 30, 2025
51 of 54 checks passed
@aelovikov-intel aelovikov-intel deleted the bf16-conv-fixes branch September 30, 2025 13:50
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