News for hackers. Stuff that matters.

gj_78

Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @06:37PM (#24530775)
The question is not about the head count. How many software engineers at nvidia produce software that is expected run/compile on the host CPU of the customer, like this library ? I expect not too much.
Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @03:05PM (#24529710)
I did not say the library controls anything, Nvidia controls the library : its features, its roadmap, its bugs corrections, development efforts (people) etc. All these choices are made by Nvidia. It is not just another tool , it is the tool that is closest to hardware evolution.

Nvidia buying ARM is not a good news for me. The same way I don't like them making software, I also don't like them selling CPUs or seafood. They are good at GPUs and that's OK.

The drivers are usually running in the kernel space and do not involve much of interaction with users. Firmware, on the other side, is hardware-close software and can be gradually replaced by specific hardware continuous improvements without the user/software or the OS noticing.

Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @02:34PM (#24529518)
> You don't think developers should be able to write C++ code for the GPU?

To be clear, I don't think nvidia-paid developers should be able to write C++ Code for a nvidia-sold GPU. The world will be better if any developer (paid by nivida or not) is able to write code for any GPU (sold by nvidia or not). It is not nvidia role to say how or when software will be written. Their hardware is good and that's more than OK.

AI/CUDA code written specifically for nvidia is useless/deprecated in the long term. A lot of brain waste.

Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @01:23PM (#24529023)
Sorry, related to cpu and host memory , I was wrong. I meant : having the GPU seller control/write code that plays with host cpu and memory is bad. Let people use their own gcc/g++ or whatever compiler and publish the specs. Unless they also start selling CPUs.
Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @01:22PM (#24529003)
Again, I see what you mean. I am even against nvidia advising the developers to use such or such C++ library (be it GNU). It is not their role to do that. We need smarter and more shining GPUs from nvidia, not software.

I would say .... The hardware must be sold independently of the software ... but it is a bit too complex, I know.

Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @11:19AM (#24527979)
IMHO, the question is not that we need code to run on CPUs and GPUs , we do need that, The question is whether the GPU seller has to control both sides. Until I buy a CPU from nvidia I want to keep some kind of independence.

When will we be able to use a future riscv-64 CPU with an nvidia GPU ? we will let the answer to nvidia ?

Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @09:46AM (#24527380)
Raspberry Pi is not marketed for graphics as nvidia is doing with their GPUs. What I mean is that firmware is running on a usually small cpu and memory that is sold as a part of the GPU. No security issues here as the main security issue is to plug the whole GPU inside your PC.
Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @09:32AM (#24527297)
A lot of hardware has builtin software, either inside a firmware or as a driver. Keeping the software part in firmware lets customer free to use any kind of OS. Using host cpu and memory is bad design IMHO.
Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @09:10AM (#24527178)
Agree++. They are good at hardware and should stay that way.
Re:Libcu++: Nvidia C++ Standard Library on Saturday September 19, 2020 @08:59AM (#24527126)
I really do not understand why a (very good) hardware provider is willing to create/direct/hint custom software for the users.

Isn't this exactly what a GPU firmware is expected to do ? Why do they need to run software in the same memory space as my mail reader ?