It probably wasn't obvious from my earlier comment, but I was comparing SiFive to ARM and then I was comparing SiFive with other RISC-V IP vendors (and open source projects.)
Personally I'm more curious about RISC-V in tiny microcontrollers, and were I guiding semiconductor strategy I'd be way more concerned about ability to build embedded systems than GPU farms. The ecosystem to do the former can evolve into the latter, but skipping to the end is just a route to burn absolutely billions.
IIRC, the RISC-V spec includes an "embedded profile" that specifies a CPU with 16 32-bit registers, so that should make RV32 even smaller than it would be otherwise. SiFive designed a dog-simple 2-stage pipeline 32 bit core that could even run without I-cache. I mean, it's not a speed demon, but it was implementable in many fewer gates than their earlier E cores.
I worked at SiFive for a year and couldn't make sense of their product strategy. But maybe that's a me problem and not a SiFive problem.
I really do sort of wonder what they're doing with 175m in Series F funding. Where do you go from there?
The only true thing that could be done is to have some top secret insight into CPU design optimization and apply it to RISC-V guiding the actual open spec along with you as necessary. Which is close to what Apple appear to have done with ARM64, but then Apple did hire/acquire an absolutely incredible team to get them there, and have the money to reward them.
It's certainly not impossible, but it seems a tough row to hoe.
But the cool part of this is that the ISA and many supporting packages (rocket, boom, etc.) are "open" and "free as in beer." Even if SiFive did fail, an IP investment in RISC-V would not necessarily have been a bad move. Which is why I said I'm fairly bullish on RISC-V (cause even if SiFive fails, customers existing investment in the ISA is not lost) but bearish on SiFive (because I fear their existing valuation may be too inflated.)
I'm not trying to tell anyone their SiFive baby is ugly. I'm not saying designing a RISC-V solution is a bad move. I'm just saying from my perspective, with incomplete information about what's going on inside SiFive, it looks like they have a difficult road ahead. I would POSITIVELY WELCOME any information regarding reference customers or catalog parts which might imply there's a large customer who's signed on the dotted line to pay SiFive a royalty for using their designs.
Full disclosure: I own no SIFIVE stock (or options) nor do I own stock in any company that competes in the RISC-V design space (Esperanto, Andes, Sandisk/WD, etc.) I still have stock in TXN though, but I haven't heard that they're deep in RISC-V. I am a former employee of SiFive, but was not employed in a management position; don't take my comments as being based on "inside information."
How about SERV... That core can be configured to not use a register file (everything stored in BRAM).
SERV takes 32 clock cycles for most instructions, 64 cycles for some such as shifts and branches.
Yes, there are some things SERV is fast enough for, but E20 is not all that much slower than 5-stage pipe plus branch prediction E31 -- E20 does 1.2 DMIPS/MHz compared to E31 1.6 (and Arm Cortex M0+ 0.95, M3/M4 1.25)
Never heard of this despite being casually interested in hardware, it is apparently this?:
https://ocw.mit.edu/courses/6-004-computation-structures-spr...
Via MPW and assembly service one can easily have that die manufactured, packaged and mounted on custom PCBs for under $50K, a.k.a. much less than you'll pay in salary to have it designed, fabricated and tested. Even at non-American labor rates.
In 2023 producing a computing core, albeit not a state-of-the-art one, is just not the moat it once was...
I'm not saying "building a RV32x is impossible," I'm saying there are people with existing tool-chains that favour Verilog or SystemVerilog (or even VHDL, though I don't know of them personally.) And telling them "no, you should use Scala / Chisel / Firrtl to model the features you want to add to the system in order to meet customer requirements" is kind of a hard sell for many customers.
However, RISCV cores abound. In pretty much any HDL known to man with varying design trade-offs and capabilities. It's extremely difficult to differentiate at the RTL level at this time. Not impossible, but it would be a significant investment, which is I guess SiFive's business model. Sell IP at prices cheaper than that.
Here is a high quality, well documented, SystemVerilog version intended for embedded applications that I know has been included in multiple ASIC and FPGA designs successfully.
Well, you drove a Bambino on a 60 miles each way commute over a huge hill, so there's something questionable going on there :p
I can't see much wrong with the "start with microcontrollers, work your way up to single-issue Linux-capable, then dual-issue in-order, then small then bigger and bigger OoO" strategy.
What else can you do? Try to take on Xeon day #1?
On the other hand, sure, you can ask a lot of questions about how you take that to the market, and who the customers will be.
SiFive early on obviously thought there were a lot of people out there who really wanted to make little custom chips for this and that but didn't have the skills, and SiFive (via buying OpenSilicon) could provide a one stop shop. And even provide a lot of automation around that, in the SiFive Chip Designer -- there used to be a web page (similar to SiFive Core Designer) but it's long gone, but see e.g. this Yunsup's presentation https://www.youtube.com/watch?v=pxd93jb1OAk
It seems no one really wanted to do that -- or at least SiFive didn't find them. So they got rid of OpenSilicon again (at a HUGE profit) and seem to be just selling CPU core IP to people who were already making chips, had all the people and knowledge to do that, but just wanted to change away from Arm or Tensilica or 8051 or whatever.
> what they're doing with 175m in Series F funding. Where do you go from there?
That's still absolute chickenfeed compared to what Intel or AMD or probably Arm spend on designing a single core.
I'm talking more about how they thought they were going to interact with customers w/ a design language no one seemed to want to use. I think we agree on that; NO ONE seemed to be asking for Rocket / Scala / Chisel / Firrtl and it seemed odd that every time a potential customer asked for Verilog, they kept pushing Chisel.
But now that they're not pushing the core designer, how are they justifying their multiple? They're no longer a SaaS play, they're an IP design play which makes it a lot more difficult to hit the rule of 40.
But Intel famously passed on the $2B offer, which means they have to do something to convince someone out there they ARE worth whatever their post-money, round F valuation is lest the round C investors lose money and the round A investors not make as much money as they had hoped.
And yes $175m is less than ARM spends to design a core, but that's not what the $175m round F was for. Or at least I hope it's not what it's for, 'cause if they did sink it into designing a core that's just now on par with ARM's a72 (or was the recent goodness supposed to be on par with the a77?) from 4 years ago, what's the motivation for using a RISC-V core instead of an ARM core?
"We're as good as ARM was 4 years ago" isn't a great marketing slogan.
Your information about the details of the OpenSilicon spin-off must be better than mine. "Huge" profit is not what I heard. But neither of us were in San Mateo when that happened.
I would LOVE to be able to buy a part that lets me test any of the recent cores (I mean for less than $100,000.) Or I would love to hear about any customers using the new cores. It shouldn't be that hard to find a reference customer.
By the way StarFive were SiFive China until SiFive divested them (the split was a bit acrimonious).
They are making peanuts compared pretty much all companies that actually make chips. Their IP seems to be worth much more than the business.
I'm not even sure what the valuation this valuation might even be based on (which admittedly applies to a bunch of other companies which actually end up doing quite well). They might conceivably be worth 100 P/E as an acquisition but an IPO would only make it less likely?
$50-55 billion would mean that ARM is more overvalued than Nvidia and Nvidia actually has a realistic chance to grow into that valuation.
I can't see how Arm is even worth the $32 billion SoftBank paid for them now. RISC-V didn't exist outside of Berkeley in 2016 when SoftBank bought Arm, but now it's becoming a serious rival and especially a serious limitation on how much Arm can raise prices.
Arm have around 2.7 billion in annual sales with $500m or $600m of profit.
That makes $32b a P/E ratio of 50 to 60, and $50b a P/E ratio of 80 to 100.
In simple terms, if you pay $50 billion to buy Arm, and they make the same profit every year as they are making now, it will take 80 to 100 years for you to make your investment back.
It's like putting your money into a bank paying 1% interest, but a lot riskier.
Such P/E ratios can only be justified by the company and its profits growing rapidly.
Arm's revenue actually fell 1% from 2022 to 2023. The last four years have been roughly 2.0, 2.7, 2.75, 2.7.
Is that a peak, and it's only downhill from now on, because of RISC-V (or otherwise). Or will they start to grow again?
Either way, it sure doesn't look like the very high annual growth rate needed to justify a price of $30b let alone $50b.
But that's not how you make money by purchasing companies. You make money by buying the company low and then selling the company high. So if you bought ARM for $50B and sold it for $70B in 5 years, you would make $20B on an investment of $50B
But I'm certainly not in the position to guess how much ARM would appreciate over the next 5 years. I pulled that example out of a hat (or some other, less polite to mention part of my anatomy.)
Fundamentals count for something, no?
On the one hand you have ARM investors wanting them to extract more revenue, and the ARM customers do not want to pay more or have more restrictive licenses. They are in a bit of a nasty equilibrium but one that will hit all IP companies eventually.
An old colleague of mine has got into the idea businesses are now going to put the big squeeze on all suppliers that count as part of gross margins, which would include ARM, while essentially ignoring operational costs. The implication would be companies looking to use RISC-V would be more inclined to pay chip design houses on a contract basis more upfront than have anything including royalties. I dislike the idea but think he is right, and that the future of electronics is about to go through the same sea change that software did with open source and the emergence of SaaS.
ARM is a fabless pure play IP house. The big bucks are not in IP design but in manufacture.
That's another thing they have in common with Arm.
RISC-V is only interesting as a platform for a different business model.
Nevertheless it seems plausible there are companies that would like to license a RISC-V design (rather than implement their own or use one of the slower free cores) and might therefore be a SiFive customer. I'm not saying it's going to be a huge market, probably a much smaller one even than Arm, but it's a possible one.
I think part of what I'm getting at is it's TOUGH to get people to adopt new IP. And it's TOUGH to be all things to all people so you can compete in the low end against M0s and MSP430s, in the mid range against A77s and in the high end against i9's.
That being said, if SiFive fabbed a catalog part with one or two E20s at a reasonable cost, I have an immediate need of 200 of them. I only wish there were another 500 of me with a similar need so there was a chance we could get it fabbed at a decent price.
Why would they do that? That's not the business SiFive is in. Arm doesn't do that -- they leave that to people such as the Raspberry Pi Foundation with the RP2040.
Perhaps (if you insist on a SiFive core) you could look at something like the BL602? $0.99 here.
https://pine64.com/product/pineseed-bl602-wifi-ble5-soc/
If you're willing to use non-SiFive cores (and why not), the CH32V003 is pretty awesome for $0.10 (8 pin) to $0.14 (20 pin), assuming 2K RAM and 16K flash is enough for your purposes.
But I don't know what is "a decent price" for you.
If ARM decides to change their license terms, you are screwed. If SiFive decides to change their license terms, you could just switch to a competing IP vendor without any changes to your software ecosystem.
But yeah. Even though we have compilers, it's not like you can spin up support for a new ISA in the drop of a hat. If you launched a project with a StarFive part and then decided you wanted to use SiFive IP, you should be able to use the same tooling. The impact of that shouldn't be under-estimated.
Go x86, and you'll end up dealing with Intel, or AMD (okay, there's Via & maybe a few makers of legacy x86 parts).
Go RISC-V, and roll your own or pick from a growing list of vendors, are both valid options. And switch supplier while keeping your toolchain ecosystem.
I'd expect at least that this will spur innovation in the field. Likely increase consumer choice.
More suppliers of [insert product type here] is almost always a good thing.
And the specs extend further to non-ISA, such as standardizing boot process and platform.
If that is what you're saying, I think you're wrong.
As to the low level hand coded assembly. There's a fair amount of stuff in the Intel architecture that's not officially published. There are tools (from Intel) like VTune and the Intel C compilers that use non-published interfaces to optimize C or assembly, sometimes significantly. It is true you can write software without them, but many people purchase these Intel tools to make sure their systems run quickly and efficiently.
I can't remember if the SiFive U-X4 core equivalents were defined in the open RISC-V specs or as part of SiFive specific interfaces. If the former, then your point is even stronger. If the latter, your point is still valid, though modulo the impact of having relied on a SiFive specific interface.
Yes. That's where the big money is. It seems their current top-of-the-line core is on par with an A72 or A77. I'm not sure how it stacks up against an Apple M1.
My take on SiFive is it's at the point that it COULD compete, but they have to get more mind-share. If you're Samsung or Apple (or MediaTek or Allwinner or Rockchip or ...), you probably have experience with the ARM ecosystem and tools. Presumably you have a history with a business model and have factored in whatever royalties you're paying ARM into your cost of operations. It's a risk to set that aside and start using a different architecture, so you would want to have some quantifiable benefit before you ditched ARM for RISC-V.
It seems to me that clearly elucidating that benefit to potential customers is an important part of this equation. SiFive's earlier designs seemed to have smaller PPA numbers, so that's nice. But they were for in-order execution w/o macro fusion or speculative branching, so they were a little closer to A53s in performance per watt. If you had a RV64 design with the performance per watt of an A77, but with a power/area budget 20% lower, that might have a REAL impact on yield and cost.
That would be a thing to crow about. But that's not the type of crowing I see happening on the SiFive web page.
I keep thinking a catalog part with maybe a pair of U-54s, a pair of 270s and a pair of 670s plus typical SoC peripherals would be a great way to introduce developers to what SiFive designs could do. They could give dev boards to Samsung, Zero, Google, LTE engineers who could tweak the existing android RISC-V android images to get an idea for performance and power use.
Maybe they could sell Apple on the idea of acquihiring SiFive. Apple's never been skiddish about changing processor architectures or suppliers.
So... to recap... I'm thinking catalog parts mostly as a vehicle to prove to potential customers your IP can be fabbed to meet their power / performance / yield / cost targets. And if I can buy a couple hundred of these boards for a different project, then I'm even happier.
Their current core, the P870 (the subject of the post we are commenting on) is on par with Cortex X2, announced just over 2 years ago in May 2021.
A76 class was the P550, announced in June 2021, 3 years after the A76's May 2018 announcement.
A72 class was their U84, back in October 2019, 4 1/2 years after the A72's February 2015 announcement.
The time gap has been coming steadily down.
All of these cores, both Arm and SiFive, take about four years to get into cheap mass produced catalog part chips and boards e.g. the A76 RK3588 just started appearing in SBCs around May 2022. A72 to Pi 4 was 4 1/2 years.
I don't know how much you can pick up a JH7110 with four 1.5 GHz U74s (plus that S7) for, but Milk-V are selling a compute module board with one for $34
https://arace.tech/products/milk-v-mars-cm?variant=423421722...
Oh I don't disagree, lowering the cost to field a system out of your micro-architecture increases the likely hood a design engineer will design it into their own design. This effect singlehandedly sustained the x86 product line until it didn't.
The RISC-V B extension's `sh2add` and friends make a small difference -- that's basically the 2.7% gap between the VisionFive 2 and the HiFive Unmatched. If I disable Zba on the VF2 then the times are just about identical.
But yes... this led us to a working style where we tried very hard to avoid having to use rocket or boom generators. I didn't want to be in the business of maintaining RISC-V Verilog tools. At around the same time we realized RISC-V was overkill and built a very poorly designed Lisp DSL which output Verilog for a dog-simple 6-bit controller. Not an ideal solution to be sure, but it worked better for us than spending a couple years learning Rocket/Scala/Chisel.
Nick Tredennick (who I believe was the main designer of the 68k) has a quote in his book "Logic Design: The Flowchart Method":
The problem with many texts is that we lie about
details. We are sloppy in areas that are not our primary
concern. Academics are method fanatics. Practitioners
are solution fanatics. In school, we glorify the methods
and lie about the sophisticated problems we solved. In
industry, we glorify the problems and lie about the
sophisticated methods we used. Each side loses
credibility the minute one side reads the other's
literature. The academic knows that the practitioner's
"method" is (ugh!) arbitrary, just as the practitioner
knows the academic's "solution is (ugh!) not applicable.
Because we oversell method and solution, it takes too
long to figure out what really works.
I don't want to say Rocket / Chisel / Firrtl is bad, but it always seemed to be more in support of a "process focused" methodology than the "solution oriented" focus I'm used to. If it works for you, I'm absolutely not going to tell you it's a bad idea to use it. It's just too much overhead for the small projects I work on.That being said... SiFive was working on CoC (theorum prover) extensions to validate designs using formal methods. THAT sounds fascinating, but I'm not sure how they would monetize it.
[Edit: To recap, I don't have a problem with Rocket / Chisel / Firrtl per se, but they operate at a level I'm uncomfortable with and seem to be less stable than I would prefer. I completely understand this is not the case for many other people.]
Synopsys seems to think it's a decent business to be in. :)
https://www.synopsys.com/verification/static-and-formal-veri...
So... their cores are great, but if I'm only going to see them if I write a very large check to SiFive, they're sort of irrelevant to my world. I would love to have SiFive IP that doesn't use Rocket/Scala/Chisel and does produce catalog parts.
That could be just me. I enjoy getting my hands dirty.