News for hackers. Stuff that matters.
Re:RISC-V port submitted for inclusion in GCC by gchadwick on Thursday January 12, 2017 @06:32AM (#13381450)
Part of the problem is to produce a high-end RISC-V chip doesn't just need the RISC-V core. It needs all of the supporting IP as well which can be substantial (interconnect, system caches, memory controllers, peripherals etc). Plus to produce something that can complete with modern mobile APs you'll need to fab on a modern process (e.g. 28 or 20nm, though that's a bit long in the tooth if you're targetting things coming out rather than matching current technology, 16FF would be better) which increases costs substantially. Simple, slow, microcontrollers can be fabbed on older and far cheaper processes.
Re:RISC-V port submitted for inclusion in GCC by bogomipz on Thursday January 12, 2017 @07:58AM (#13381826)
">16FF would be better"

Did you mean 16NM or are you referring to something else other than process size?

Re:RISC-V port submitted for inclusion in GCC by rrmm on Thursday January 12, 2017 @08:03AM (#13381858)
Re:RISC-V port submitted for inclusion in GCC by gchadwick on Thursday January 12, 2017 @09:08AM (#13382254)
rrmm is correct. 16FF is generally used to mean the 16nm FinFet process.
Re:RISC-V port submitted for inclusion in GCC by bogomipz on Thursday January 12, 2017 @01:40PM (#13384882)
Ah OK I am glad I asked thanks then, thanks for link too.