News for hackers. Stuff that matters.

0x1DEACAFE

Re:RISC-V on the Verge of Broad Adoption on Thursday February 14, 2019 @06:01PM (#19166916)
meh. i think the unit count is down to about a thousand. also strongly dependent on what node size you use. 180nm and 350nm are pretty cheap these days. but you're probably only off by an order of magnitude if you're talking about 28nm (which is what the SiFive HiFive Unleashed chip uses.)

but... your point was probably more along the lines of "getting custom silicon is still going to need a market of greater than several thousand," and that's probably always going to be true.

Re:RISC-V on the Verge of Broad Adoption 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.
Re:RISC-V on the Verge of Broad Adoption on Thursday February 14, 2019 @05:41PM (#19166783)
I think this is wrong. Certainly the GCC toolchain spits out some remarkably mediocre code. RISC-V compressed is generally on par with Thumb2, and where it differed, Thumb2 seemed to be a tiny bit more dense.

If you compare GCC/ARM with GCC/RISCV the difference isn't too great, but even the IAR ARM compiler gives you noticeable improvements over GCC/RISCV. And ARM's compilers are actually quite good with respect to code size; MUCH better than GCC/RISCV (or even GCC/ARM).

That being said, were I to add some custom instructions, I would COMPLETELY prefer to do it with RISC-V than with ARM.

[] Though the gcc/riscv toolchain is getting better pretty quickly.

Re:RISC-V on the Verge of Broad Adoption on Thursday February 14, 2019 @05:33PM (#19166722)
Yup. Everything you say is true.

I would add though there are a couple places in the low end where one or two cents seem to matter. Or at least product managers think that it matters.

In the mid-range, RISC-V providers (certainly SiFive) are pushing the idea that it's easy/easier to add custom logic to your RISC-V based die. I'm not able to judge whether that's really true, but since they're starting with a clean slate in terms of interface logic then maybe. I can't imagine it being harder to add your own tile to a RISC-V design than an ARM design.

The tools seem to me to be pretty primitive, though. IAR says they'll have a compiler soonish. GCC still emits some "not completely great" code. (I mean, don't get me wrong, it's not horrible, but compared to the mature toolchains like ARM, Intel & MIPS, it's kind of bad.) Though it's certainly getting better over time.

If you look at the architecture though, it does seem a bit easier to implement than ARM and there's more to open designs than just the "free as in beer" argument.

RISC-V seems to be appealing to people who have a strong desire to "play around with" an architecture or a solution or are financially motivated to add logic that's somehow hard to add to ARM.