News for hackers. Stuff that matters.
Re:RISC-V on the Verge of Broad Adoption by ip26 on Thursday February 14, 2019 @03:13PM (#19165533)
I'm sorry, did you just describe the core advantage of a new RISC CPU against incumbents as smaller code size? Where am I, and what is happening?
Re:RISC-V on the Verge of Broad Adoption by wmf on Thursday February 14, 2019 @05:13PM (#19166583)
RISC-V has a code compression extension so it's not classic RISC but it's still far simpler than CISC. https://riscv.org/wp-content/uploads/2015/05/riscv-compresse...
Re:RISC-V on the Verge of Broad Adoption by imtringued on Thursday February 14, 2019 @04:25PM (#19166204)
That's a pretty damn good argument. It's 10% ahead of the best ISAs that took decades of development. Just think of how adoption would be affected if it was 30% worse.

In other words: not only is it better in terms of royalties and ecosystem, it also better at everything else too. Isn't that terrific?

Re:RISC-V on the Verge of Broad Adoption by marcosdumay on Thursday February 14, 2019 @04:46PM (#19166371)
I read the GP as talking about how code size was always a weakness of RISC, and seemingly the largest one.

And here it is compared against a classical CISC platform and a hybrid one highly optimized for code size, and winning. What just makes RISC-V even more awesome than just any non-optimized design beating the incumbents.

Re:RISC-V on the Verge of Broad Adoption by dbcurtis on Thursday February 14, 2019 @04:10PM (#19166060)
Is it a core advantage? Maybe. But smaller code size has beneficial effects on the silicon cost. Choice 1: If you can benchmark the same on important work loads with 10% smaller I-Cache, make the die smaller. Manufacturing costs go down with a greater than square law effect with die area. Choice 2: Use the die area freed up to put more functional units in the same area.

Core advantage? I will let others debate that. Significant: surely.

Re:RISC-V on the Verge of Broad Adoption by pcwalton on Thursday February 14, 2019 @07:20PM (#19167415)
x86-64 isn't very space efficient anymore, so it's not hard to beat. Even AArch64, with a fixed 32-bit instruction size, competes well with x86-64.

REX prefixes really killed the space efficiency of the x86 architecture.

Re:RISC-V on the Verge of Broad Adoption by zerohp on Thursday February 14, 2019 @03:57PM (#19165939)
Smaller code size makes your caches more effective. L1 instruction cache is size limited because it's on a critical timing path. Increasing its size limits your operating frequency.
Re:RISC-V on the Verge of Broad Adoption by hrydgard on Thursday February 14, 2019 @03:43PM (#19165799)
Still matters in many embedded applications.
Re:RISC-V on the Verge of Broad Adoption by 0x1DEACAFE on Thursday February 14, 2019 @05:46PM (#19166818)
Code size for RV32IMAC is still pretty mediocre with the current GCC/RISCV compiler. And the standard library they use by default is pretty sub-optimal. I know they're working on it, and it's clear they're making quick progress, but it's not easy at the moment. The last project I worked on, I had to abandon ABI conventions and hand craft large chunks of code.