-
Notifications
You must be signed in to change notification settings - Fork 787
SYCL_INTEL_bf16_conversion spec #4237
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
Conversation
Signed-off-by: Alexey Sotkin <alexey.sotkin@intel.com>
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We aren't expecting to have any numerical limits for bfloat16 type, are we?
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
Spec: intel/llvm#4237 Implementation: intel/llvm#4213 Signed-off-by: Dmitry Sidorov <dmitry.sidorov@intel.com>
Default constructor, copy constructor and destructor are explicitly declared as defult. Add clarification that the extension is an optional kernel feture Rounding mode is specified Minor improvement to the example Fix a typo
This extension doesn't define the |
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
Currently this aspect is mapped on a device info which is being proved by get_platform_name function, claiming, that any Intel GPU device supports BFloat16 extension. Once we have a lower-level spec we can re-map it on the appropriate OpenCL extension. Spec: intel#4237 Signed-off-by: Dmitry Sidorov <dmitry.sidorov@intel.com>
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
Add explicit conversion functions Add operator overloadings Apply code review suggestions
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
sycl/doc/extensions/Bf16Conversion/SYCL_INTEL_bf16_conversion.asciidoc
Outdated
Show resolved
Hide resolved
Remove `uint16_t` constructor
I notice that the SYCL extension here defines comparison and arithmetic operations, but (1) is named "conversion" in the extension name and (2) the SPIR-V extension includes only conversions. Are math/comparison ops already handled in SPV somehow, and should we rename the SYCL extension to be something more general than "conversions"? |
@mkinsner thanks for feedback.
No, we have only conversion in SPIR-V. Math/comparison is done on
Makes sense. Any ideas? |
+1 |
Spec: intel/llvm#4237 Implementation: intel/llvm#4213 Signed-off-by: Dmitry Sidorov <dmitry.sidorov@intel.com>
Spec: intel#4237 Implementation: intel#4213 Signed-off-by: Dmitry Sidorov <dmitry.sidorov@intel.com>
Signed-off-by: Alexey Sotkin alexey.sotkin@intel.com