4 ms·
So this feels like it begs the question: What's the big deal with RISC-V if this exists? If we've had a Linux-capable BSD-licensed patent-free processor since 2
by yjftsjthsd-h 6y ago
So this feels like it begs the question: What's the big deal with RISC-V if this exists? If we've had a Linux-capable BSD-licensed patent-free processor since 2015, why did we spend so much time and effort and money to make another completely new ISA?
- chasil 6y agoNotice that it does not implement an MMU, nor was 64-bit ever implemented in the instruction set.
- yjftsjthsd-h 6y ago> J2 is a nommu processor because sh2 (the processor in the Sega Saturn game console) was, and the last sh2 patent expired in October 2014. The sh4 processor (dreamcast) has an mmu, but the last sh4 patents don't exire until 2016. (Update: we're probably implementing a simpler MMU design which will run the same userspace software but require kernel and QEMU updates, which we'll submit upstream when ready.) Seems like it was in the pipeline, and still should be easier to add an MMU to a fully-fleshed system than create a whole new ISA. For that matter, there are plenty of RISC-V implementations without MMUs, aren't there? So they should be exactly the same. The 64-bit thing I'll give you, although it isn't obvious to me how much that would matter for most places where people are using ARM or RISC-V so far; it limits you to 4G of memory, but in embedded uses (phones, routers, raspberry pi) who cares?
- freemint 6y agoThey started before RISC-V existed. The reason why they build their own implementation of an CPU and not used some open Mips or Sparc is that they found that those used to much BUS bandwidth for their use case. SuperH was really well designed architecture with really good instruction set density. Instruction set density is not a thing tagged on to a spec which many cores don't implement and if it is implemented you end up having a mess of mixed 32 and 16 bit instructions. SuperH is cleaner in that everything is a 16 bit instruction which helps with making decoder cheaper.
- yjftsjthsd-h 6y agoBut that's an even stronger reason for j2 to have taken off and risc-v to never be created, isn't it? So what went wrong?
- monocasa 6y agoSH processors are very good contenders in their specific gate count niche, but have a lot of headaches for implementing higher performance cores that RISC-V was attempting to explicitly address. A lot of exposed pipeline kind of stuff. Only specified a soft fill TLB. The ISA is very constrained by being 16-bit only that gets in the way of density when compared to other more modern instruction bandwidth conscious RISCs (although it can't be stated enough how much SH inspired all of the later examples, including Thumb and RV-C). Additionally SH variants with full MMUs would have lost their patent protection after RISC-V was already released and gaining steam.
- freemint 6y agoVery good summary. One example of such an head ache would be the branch delay slot. It works really well if you have the compiler perform an reorder of instructions for you so the chip can do more while waiting for memory. In a modern pipeline CPU with register renaming, out of order execution this ISA level reordering would be at best complicating the implementation. The branch delay slot makes sense where you aim to wait 1-3 cycles for memory loads but becomes a meaningless complication in the face of 10's or 100's of cycles waiting for memory seen on high clocked CPUs today.
- Symmetry 6y agoSure it's an open ISA with some advantages but if I was going to have an undergrad design a small processor in a single semester I'd certainly go with RISC-V just because it's so simple and regular. And likewise with a simple out of order processor for a grad student or senior project. And then there' the design for extensibility and only implement what you need that makes RISC-V appealing in the embedded space even apart from being free to use.