3 ms·
The floating point unit is optional on the U8, which is a non standard choice for a OoO design. Normally if you've got an OoO frontend, sticking a FPU is a dro
by monocasa 7y ago
The floating point unit is optional on the U8, which is a non standard choice for a OoO design. Normally if you've got an OoO frontend, sticking a FPU is a drop in the ocean (or can be).
Is this an artifact of them using BOOM (which is just an assumption on my part), since BOOM makes it ridiculously easy to add or remove backend execution units?
- microcolonel 7y agoI don't think U8 is BOOM-based, but RISC-V decoders are pretty trivial, so they probably had some extra time and patience to make the rest of the frontend more flexiblep
- monocasa 7y agoIt certainly reads like it's based on BOOM; they're describing BOOM's gate count niche to a tee. And their previous designs were based on rocket.
- reitzensteinm 7y agoThere are an absolute ton of customization options available. In the context of the decisions that can be made, making FP optional isn't surprising. I do have to wonder about whether they've got tools for real customers that can effectively test the tradeoffs being made, at least for performance options like cache size & associativity. Even with all the options at your disposal and an intimate knowledge of your problem domain, beating a handful of well made and broadly tested off the shelf designs won't be easy. I love this stuff, but I'm a bit skeptical if it's actually something the market is asking for. If there were more substantial options like crypto accelerators, GPGPU, video encoding/decoding, FPGA, mixing big and lots of small cores, vector extensions, being able to size up the ALU for specific operations... I could see the pain of custom silicon paying off. Having accelerators sharing the cache hierarchy is not something the big players have really done much of yet and probably won't until there's so much dark silicon they can more or less throw the kitchen sink in. https://scs.sifive.com/core-designer/customize/f9c3a7e1-08b7-464e-8bf9-39da62e2e35b/ https://scs.sifive.com/core-designer/customize/f9c3a7e1-08b7...
- brucehoult 7y agoOne benefit of having customers customize their own cores, is they can iterate their settings (on FPGA) in hours and test the result on their actual workload, not just guess how some semi-standard core might perform on their workload based on SPEC or CoreMark or something. The announcement says the U87 with (Cray-like) vector processing will be available in H2 2020.(Also ARM SVE-like, but ARM hasn't shipped anything with it yet, and I think hasn't even announced anything with it? Fujitsu has, in a supercomputer) Meantime, the U84 has only scalar integer and FP, with nothing equivalent to NEON on ARM. That might or might not matter to you. Mixing a reasonable number of cores (up to nine) in the automated SoC configuration tool was announced alongside the 7-series (dual issue in order) cores in October last year. That continues. If you want more cores than that some engineering time would be required to verify it. https://sifive.cdn.prismic.io/sifive%2F5ec09861-351b-420c-b6e3-e2b76843044f_linley+report+-+sifive+raises+risc-v+performance.pdf https://sifive.cdn.prismic.io/sifive%2F5ec09861-351b-420c-b6... Adding QuickLogic eFPGA to a SiFive core has been announced: https://www.prnewswire.com/news-releases/quicklogic-teams-with-sifive-to-make-efpga-technology-available-via-designshare-portfolio-300939385.html https://www.prnewswire.com/news-releases/quicklogic-teams-wi...
- reitzensteinm 7y agoVery cool, thank you! While you can iterate pretty quickly on an FPGA, I'd still be worried that cutting down a chip to optimize for $/perf works until it doesn't. Something off the shelf would be pretty resilient to algorithm tweaks (ad absurdum you have an Intel chip which performs black magic to run almost anything you throw at it well). It's pretty hard to overcome the economy of scale of just buying a mass produced chip that's twice what you need but ten times cheaper because they're made in batches of a million. I should note that my skepticism is coming from a place of "I want this to be a thing". Using the web page to design a chip is an instance of "live in the future and build what's missing" if I've ever seen one.
- mlyle 7y agoThis is not to beat commodity processor/controller silicon. If you are going to build a SoC for whatever reason (peripherals, integration, etc) -- you might as well make the integrated processing exactly what you want.