3 ms·
> As I understand it Nvidia's use of RISC-V was for controller cores, its not the main ISA doing the important work… Isn’t that exactly the use case the articl
by simonh 6y ago
> As I understand it Nvidia's use of RISC-V was for controller cores, its not the main ISA doing the important work…
Isn’t that exactly the use case the article is talking about?
- gchadwick 6y agoNot as I read it: > Going for custom proprietary instruction-sets is thus not a good idea (In reference to why you'd use RISCV for co-processors in general) I'm arguing the custom ISA is essential to building the co-processor (or at least makes it easier). The fact your application is super specialised means the existing RISC-V software ecosystem doesn't really help you. Nvidia's use of RISC-V is incidental, not a key part of their GPU architecture.
- simonh 6y agoIsn't that the whole point of RISC-V's ISA extensions system though, so you can use a minimal base of standardised instructions for generic stuff with established developer tooling, but still have custom application specific instructions tuned to your design?