New Nvidia driver adds 16bit float support to OpenCL [pdf] (opens in new tab)

(us.download.nvidia.com)

82 pointszbendefy2y ago15 comments

15 comments

Can someone explain why they update to Clang 7, that was released 19 September 2018?

It's very very common for software like shader compilers or AOT compilers for other languages to be based on old clang/llvm forks.

peppermint_gum2y ago

It doesn't seem it's new. The release notes for the 511.79 driver from February 2022 say the same thing:

https://us.download.nvidia.com/Windows/511.79/511.79-win11-w...

pixelpoet2y ago

It was some kind of opt-in option (which I wasn't even aware of), now it's on by default / rolled out to everyone.

zbendefyOP2y ago

It seems they are finally enable the 16bit float extension in their OpenCL implementation.

Aardwolf2y ago

Is this the IEEE float16 type or the bfloat16 type? It doesn't say

my1232y ago

IEEE

pixelpoet2y ago

https://en.wikipedia.org/wiki/Half-precision_floating-point_...

bbcc902y ago

any idea why this took them so long?

pixelpoet2y ago

Because they have a near monopoly with Cuda and get away with dragging their heels due to lack of market pressure (everyone loves to lock themselves into Cuda and then complain about GPU prices), despite having been on the OpenCL committee (just like Apple with Metal conflict of interest).

Anyway, I'm very glad to see it and will be using it immediately.

dotnet002y ago

Also because none of the competition were/are serious about OpenCL either.

AMD still doesn't have OpenCL 3.0 support and their implementation of previous versions was far far less stable than CUDA.

I can't find a definite source on this, but afaik none of the official OpenCL implementations have ever fully supported mixed CPU-GPU code the way CUDA does.

3 more replies

my1232y ago

CUDA itself only got bumped from LLVM 5 to LLVM 7 in CUDA 11.2 (https://developer.nvidia.com/blog/boosting-productivity-and-...).

LLVM 7 opt-in for OpenCL happened some time later (available since r510). What changes now is that LLVM 7 is the new default.

j / k navigate · click thread line to collapse

15 comments

Kelteseth2y ago

Can someone explain why they update to Clang 7, that was released 19 September 2018?

kevingadd2y ago

It's very very common for software like shader compilers or AOT compilers for other languages to be based on old clang/llvm forks.

peppermint_gum2y ago

It doesn't seem it's new. The release notes for the 511.79 driver from February 2022 say the same thing:

https://us.download.nvidia.com/Windows/511.79/511.79-win11-w...

pixelpoet2y ago

It was some kind of opt-in option (which I wasn't even aware of), now it's on by default / rolled out to everyone.

zbendefyOP2y ago

It seems they are finally enable the 16bit float extension in their OpenCL implementation.

Aardwolf2y ago

Is this the IEEE float16 type or the bfloat16 type? It doesn't say

my1232y ago

IEEE

pixelpoet2y ago

https://en.wikipedia.org/wiki/Half-precision_floating-point_...

bbcc902y ago

any idea why this took them so long?

pixelpoet2y ago

Anyway, I'm very glad to see it and will be using it immediately.

dotnet002y ago

Also because none of the competition were/are serious about OpenCL either.

AMD still doesn't have OpenCL 3.0 support and their implementation of previous versions was far far less stable than CUDA.

I can't find a definite source on this, but afaik none of the official OpenCL implementations have ever fully supported mixed CPU-GPU code the way CUDA does.

3 more replies

my1232y ago

CUDA itself only got bumped from LLVM 5 to LLVM 7 in CUDA 11.2 (https://developer.nvidia.com/blog/boosting-productivity-and-...).

LLVM 7 opt-in for OpenCL happened some time later (available since r510). What changes now is that LLVM 7 is the new default.

j / k navigate · click thread line to collapse