Why doesn't apple support NVIDIA though? Considering the whole ML and AI community use only NVIDIA GPUs, it sucks that we can't use apple laptops for the same.
Why would you do anything compute intensive on laptops that suffer from cooling issues?
CUDA Toolkit Release Notes
41–50 of 126 posts
Re: CUDA Toolkit Release Notes
#42We need a CUDA alternative for non NVIDIA gpu's, specially on a Mac.
AIUI, Vulkan can be used for compute - so why not do that? It might work reasonably well on both nVidia and non-nVidia hardware. Of course, this requires GPU-enabled software to implement Vulkan support, but that's one-time work.
Among the difficulties we encountered, I recall the need to use an offline optimiser to do trivial things like CSE and constant folding. CUDA and OpenCL will do this during kernel compilation, but Vulkan implementations seems to be designed as non-optimising (in order for loading to be faster, I assume). This is a perfectly understandable design, but it means it's a little more awkward to use. For direct programming (as compared to a compilation target), it's a lot more awkward.
Another issue was that basic Vulkan is very restricted, as I assume it's supposed to be usable on simple hardware. Additional functionality can be enabled through a collection of extensions. One particular problem I recall is that our code generator assumes the existence of general pointers, for example such that the same memory can be used for different types of values at different times. SPIR-V has/had a very strict notion of pointers, and no way to cast between different types without an extension, and that extension was IIRC not implemented by NVIDIA or AMD. There were lots of these kinds of issues.
In the end, Vulkan is usable for compute - after all, a single master's student (admittedly one who's very bright) managed to implement a Vulkan-targeting compiler backend in half a year. However, at the time I concluded that it's not as mature or as practical as CUDA or OpenCL, for reasons that seem perfectly solvable. However, for direct programming, the SPIR-V that is needed for shaders is completely inaccessible. It would be like writing machine code (not assembly) by hand. I assume graphics programmers have some layer on top to provide a sane interface, but since we were writing a compiler anyway, it wasn't a big deal for us.
Re: CUDA Toolkit Release Notes
#43Submitted title was "Nvidia drops support for CUDA on macOS". We changed that for a while to "CUDA 10.2 is the last release to support macOS", which is language from the article itself. Since then someone emailed and asked why the title was like that in light of the discussion at https://news.ycombinator.com/item?id=21617016 , so I've reverted to the article's title. Edit: If the article were more a burying the lede…
(title at the time of my comment was "CUDA Toolkit Release Notes")
Re: CUDA Toolkit Release Notes
#44This is why CUDA and NVIDIA are a cancer. Such an important piece of infrastructure for both graphics and ML should be open source.
Re: CUDA Toolkit Release Notes
#45Submitted title was "Nvidia drops support for CUDA on macOS". We changed that for a while to "CUDA 10.2 is the last release to support macOS", which is language from the article itself. Since then someone emailed and asked why the title was like that in light of the discussion at https://news.ycombinator.com/item?id=21617016 , so I've reverted to the article's title. Edit: If the article were more a burying the lede…
It seems like it has went from something rare, only used in very clearcut cases to something you use daily.
Re: CUDA Toolkit Release Notes
#46We need a CUDA alternative for non NVIDIA gpu's, specially on a Mac.
OpenCL is decent, and although it's deprecated, it's probably going to continue working for years. It's not as nice as CUDA for direct programming, but don't most people access CUDA through higher-level libraries anyway? You probably would not be able to tell whether those use OpenCL or CUDA behind the scenes.
Re: CUDA Toolkit Release Notes
#47Fully understandable..anyways none is doing ML on Apple hardware due to ATi Chipsets.. last Apple HW with Nvidia graphic cards are old or running Linux or Windows with Bootcamp anyways
In my understanding, Radeon Instinct cards are not doing that bad. Yes, they're not supported by CUDA, but they're not slouching either.
Re: CUDA Toolkit Release Notes
#48Fully understandable..anyways none is doing ML on Apple hardware due to ATi Chipsets.. last Apple HW with Nvidia graphic cards are old or running Linux or Windows with Bootcamp anyways
In my understanding, Radeon Instinct cards are not doing that bad. Yes, they're not supported by CUDA, but they're not slouching either.
Re: CUDA Toolkit Release Notes
#49Fully understandable..anyways none is doing ML on Apple hardware due to ATi Chipsets.. last Apple HW with Nvidia graphic cards are old or running Linux or Windows with Bootcamp anyways
In my understanding, Radeon Instinct cards are not doing that bad. Yes, they're not supported by CUDA, but they're not slouching either.
Re: CUDA Toolkit Release Notes
#50Submitted title was "Nvidia drops support for CUDA on macOS". We changed that for a while to "CUDA 10.2 is the last release to support macOS", which is language from the article itself. Since then someone emailed and asked why the title was like that in light of the discussion at https://news.ycombinator.com/item?id=21617016 , so I've reverted to the article's title. Edit: If the article were more a burying the lede…
Why is the threshold for changing urls and titles lowering all the time? It seems like it has went from something rare, only used in very clearcut cases to something you use daily.