On 7/15/2022 3:15 AM, Bruce Hoult wrote:
> So , apparently, does RISC-V, as those 10 billion cores shipped aren't
> in laptops or phones.
>
FWIW:
* The core ISA design makes sense for microcontrollers;
* Laptops and phones would imply competing with both ARM and Intel
** I don't think this fight would be "winnable" at this time.
At least for the base ISA, it is possible to implement RISC-V cheaply.
* RV32I or RV64I doesn't ask too much of an FPGA or ASIC
* RV32G or RV64G would ask a little more though.
Getting decent performance at low cost seems difficult.
* Going superscalar isn't free.
* This is why my own efforts ended up going VLIW.
** VLIW allows speeds closer to a superscalar, but at lower cost.
*** (Apparently would be 'LIW' by the original terminology though).
** Nevermind if it makes things a bit harder for the compiler.
** Did keep some RISC-like features though in the design.
*** Interlocks and Branch-Predictors are worth their cost.
** Also designed things to still run RISC-like code reasonably well.
*** Does not adversely effect performance or code density.
*** Just, RISC-style code can't exceed 1 IPC
**** This would require the mechanisms for superscalar.
* So, it seemed like a potentially interesting experiment
** Which then ate up years of my time...
** And probably wouldn't make as much sense in a PC or phone.
*** PC class CPUs are typically OoO.
*** OoO would mean the CPU effectively ignores the VLIW bundling.
** So, more: "Scalar RISC isn't fast enough, but OoO is too expensive"
Can note that my own effort also wasn't really intended for PC or phone,
and the design is not well optimized to this use-cases.
But, a lot also comes down to the relative cost and performance of
in-order superscalar (if compared with a 1-wide scalar core, or core
running a VLIW design, but, say, costing 40% more LUTs than a
similarly-featured scalar core, ...).
As for ABI thoughts:
* Not really any ideas for obvious ways to improve the performance of
the RISC-V ABI (design already seems "pretty reasonable" on this front).
Can note though that in many cases, interrupt latency may be overrated.
The cost of saving or restoring registers isn't usually enough to have a
significant impact on overall performance IME.
For most purposes, as long as the latency is much under a few kilocycles
or similar, it it probably "good enough" (except with potentially
high-frequency interrupt sources).
...
> <mailto:
jim.wil...@gmail.com>> wrote:
> >
> > On Thu, Jul 14, 2022 at 9:21 AM Liviu Ionescu <
i...@livius.net
> <mailto:
i...@livius.net>> wrote:
> > I did not follow the recent developments, was the idea to have a
> RISC-V EABI discarded? Since there is no reference to it in the
> mentioned document.
> >
> > There was no agreement on what the EABI should be, and not enough
> time and manpower to create a consensus. So it was deferred
> indefinitely.
>
> Ok, I read it as "there was no interest in a RISC-V microcontroller
> profile, so focus was kept on Unix class devices".
>
> No problem, Arm covers the microcontroller space just fine.
>
> Liviu
>
> --
> You received this message because you are subscribed to the Google
> Groups "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to
sw-dev+un...@groups.riscv.org
> <mailto:
sw-dev%2Bunsu...@groups.riscv.org>.
> <
https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/30558065-D266-4BE5-8566-EC52E3CC0A8F%40livius.net>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "RISC-V ISA Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
isa-dev+u...@groups.riscv.org
> <mailto:
isa-dev+u...@groups.riscv.org>.
> To view this discussion on the web visit
>
https://groups.google.com/a/groups.riscv.org/d/msgid/isa-dev/CAMU%2BEkz-cmiY2X5Gah8zrUwH-SWi927noKd3X-A3U_80ZXuTpw%40mail.gmail.com
> <
https://groups.google.com/a/groups.riscv.org/d/msgid/isa-dev/CAMU%2BEkz-cmiY2X5Gah8zrUwH-SWi927noKd3X-A3U_80ZXuTpw%40mail.gmail.com?utm_medium=email&utm_source=footer>.