Didn't AMD and Intel open source their drivers. Or are you talking about
firmware here?
I thought that is how OpenBSD can run well with them but not with Nvidia hw?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group a
Agreed. (Didn’t see your previous message before I sent that).
> On Jun 25, 2021, at 9:25 PM, David Riley wrote:
>
> On Jun 25, 2021, at 10:23 PM, Robert Engels wrote:
>>
>> There is also a LOT of support for Java and CUDA/OpenCL. You can essentially
>> reimplement them Java portion in Go.
On Jun 25, 2021, at 10:23 PM, Robert Engels wrote:
>
> There is also a LOT of support for Java and CUDA/OpenCL. You can essentially
> reimplement them Java portion in Go. There are multiple open source projects
> in this area.
>
> Might be a lot easier than starting from scratch.
Yes, CGo i
There is also a LOT of support for Java and CUDA/OpenCL. You can essentially
reimplement them Java portion in Go. There are multiple open source projects in
this area.
Might be a lot easier than starting from scratch.
> On Jun 25, 2021, at 8:03 PM, Michael Poole wrote:
>
> On Fri, Jun 25,
On Jun 25, 2021, at 1:32 PM, Robert Engels wrote:
>
> Why not develop a Go <> CUDA binding using CGo?
This (ditto for OpenCL, Vulkan, etc) is more likely the path you'll have to go
down. Generally all of these interfaces rely on pretty massive libraries from
NVIDIA, AMD, Intel, etc. which are
On Fri, Jun 25, 2021 at 11:52 AM Nikolay Dubina wrote:
>
> I tried to write down my own CUDA / NVIDIA GPU driver in native Go last
> weekend. To my great surprise, CUDA and pretty much all high performance
> software/hardware from NVIDIA is proprietary close-source C/C++ code.
> Meaning, you can
As others have said, lots of secret sauce which includes the instruction
set for the function blocks in silicon.
Thus there is no assembler for the compiler that generates the code. Other
chunks of the necessary tool chain are also absent or homegrown (no
document other than source).
The best adv
Why not develop a Go <> CUDA binding using CGo?
> On Jun 25, 2021, at 12:11 PM, Marcin Romaszewicz wrote:
>
>
> Graphics chips have a lot of proprietary IP, some of which the manufacturers
> would like to keep secret. If you see source for one of these drivers, you
> will have a good idea ab
Graphics chips have a lot of proprietary IP, some of which the
manufacturers would like to keep secret. If you see source for one of these
drivers, you will have a good idea about the hardware organization, so they
keep everything secret. It stinks for us developers who want to write cross
platform
I tried to write down my own CUDA / NVIDIA GPU driver in native Go last
weekend. To my great surprise, CUDA and pretty much all high performance
software/hardware from NVIDIA is proprietary close-source C/C++ code.
Meaning, you can't write native Go driver even if you wanted to. Forget Go,
peop
10 matches
Mail list logo
