4 ms·

Sure, provide a 100% CUDA-compatible chip, then do the microsoft-style EEE.

• rbanffy 3y ago
  Wouldn't a 100% Cuda-compatible toolchain suffice? Then you could write your software for Cuda and the software environment would run it on whatever is on your computer.
  • ladberg 3y ago
    CUDA the language itself isn't necessarily the biggest obstacle for porting code, it's the usage of low level hardware features. You'd have to make a chip that's pretty dang close to Nvidia's before most hand-written CUDA code could run on it performantly.
    • rbanffy 3y ago
      What is CUDA not abstracting away? Is it geometry of the SIMD pipelines or the functionalities they have that would be absent (and couldn’t be emulated) by other implementations? In many ways it feels like the same situation we had in the 70’s and 80’s personal computers, with many different software bases divided by different hardware implementations. In that regard, Unix was a boon in that it allowed one to write software that’d be compiled out of a single source into multiple architectures (rather than the PC-clone way, where non-identical implementations were driven to extinction).
• poisonborz 3y ago
  Oracle: oh no, my precious API patents!
• deleted 3y ago
  [deleted]