3 ms·
Strange that there's no mention at all of RISC-V. RISC-V also runs on FPGA, right? Does it really justify yet another RISC instruction-set? Impressed that the
by MaxBarraclough 8y ago
Strange that there's no mention at all of RISC-V. RISC-V also runs on FPGA, right?
Does it really justify yet another RISC instruction-set?
Impressed that there's apparently already a GCC backend though.
- alsadi 8y agoNot all fpgu are equal. Maybe this targets those with lower specs.
- rwmj 8y agoPicoRV32[0] targets some extremely low spec FPGAs. I have it running on ridiculously small and cheap FPGA[1] that has 8k LUTs and cost me £41 including tax and next day delivery. However I repeat what I said above: hobbyists are free to design their own instruction sets, and good on them! [0] https://github.com/cliffordwolf/picorv32 https://github.com/cliffordwolf/picorv32 [1] https://rwmj.wordpress.com/2018/03/17/playing-with-picorv32-on-the-ice40-hx8k-fpga-breakout-board-part-1/ https://rwmj.wordpress.com/2018/03/17/playing-with-picorv32-... https://rwmj.wordpress.com/2018/03/18/playing-with-picorv32-on-the-ice40-hx8k-fpga-breakout-board-part-2/ https://rwmj.wordpress.com/2018/03/18/playing-with-picorv32-...
- snaky 8y agoTo design the new ISA to be any good, is not that easy. > ARM paid millions to Hitachi to use SuperH patents in Thumb instruction set http://j-core.org/ELC-2016.pdf http://j-core.org/ELC-2016.pdf
- jimktrains2 8y agoThe second link redirected me after a few seconds to a fake Amazon site. Interesting, maybe I need to update my address to list for my host file.
- zipcpu 8y agoThe ZipCPU and several peripherals can fit within an iCE40 8k using only about 5k LUTs--and that's with the multiply unit, the divide unit, the pipelined fetch unit, and a debugging bus infrastructure. While that isn't the full pipelined implementation neither do the caches fit, it is sufficient to be competitive with the picoRV.
- TomVDB 8y agoThe picorv32 is a nice little processor, but it's surprisingly inefficient in its use of FPGA resources compared to the performance it offers (which is very low.) For small FPGAs, it's far from being the best solution. That said: there are a bunch of SOC construction tools for it, so that's definitely a redeeming factor.
- rwmj 8y agoThe project was started in Sept 2016 which was also the same month that I was first porting Fedora to RISC-V. Given the momentum behind RISC-V and also the huge amount of software now available it would obviously make sense to use a RISC-V compatible design. However hobbyists can do what they want, there's no reason to force someone who wants to design their own CPU to do it in any particular way.
- zipcpu 8y agoI actually started the project almost a year earlier, and made many mistakes before finally presenting at ORCONF in September of 2016. That said, I am considering a RISC-V compatible design. I just haven't committed to doing so.
- Tor3 8y agoRISC-V is already silicon. As in a SoC, from (at least) SiFive.
- MaxBarraclough 8y agoSure, an SoC exists, but it runs on FPGA too.
- Tor3 8y agoBut then again nearly every CPU runs on FPGA these days. 6502, Z80, various mainframe CPUs, x86, and more modern CPUs. Modern CPU development often goes via FPGA - after all, the CPU development tools are the same: Verilog, for example. Which you first synthesize to FPGA, and, after some testing rounds, to silicon.
- Uberphallus 8y agoYou may be able to run certain modern CPU units on an FPGA, maybe even one modern core, but compare the 4 million LUTs the biggest FPGA has to the 19 billion transitors a 32 core AMD EPYC has. With a LUT wildly variable equivalence of 1 to 1-50 ASIC transistors depending on the logic implemented, there's still one order of magnitude gap between them at best. In practice, Verilog simulators are used instead, they're slow as a dead horse on smack, but it's the only way to have full (logic) system integration of such big designs.
- snaky 8y ago> we verify a fairly realistic implementation of a multicore shared-memory system with two types of components: memory system and processor. Both components include nontrivial optimizations, with the memory system employing an arbitrary hierarchy of cache nodes that communicate with each other concurrently, and with the processor doing speculative execution of many concurrent read operations. Nonetheless, we prove that the combined system implements sequential consistency. To our knowledge, our memory-system proof is the first machine verification of a cache-coherence protocol parameterized over an arbitrary cache hierarchy, and our full-system proof is the first machine verification of sequential consistency for a multicore hardware design that includes caches and speculative processors. https://deepspec.org/entry/Paper/Modular.20Deductive.20Verification.20of.20Multiprocessor.20Hardware.20Designs https://deepspec.org/entry/Paper/Modular.20Deductive.20Verif...
- ballooney 8y agoNo, it is not strange that there’s no mention of RISC-V.
- MaxBarraclough 8y agoYour point?
- ballooney 8y agoFlask’s page doesn’t mention django, an avr microcontroller’s page doesn’t mention x86, my bash static site generator readme doesn’t mention wordpress... None of this is strange.
- MaxBarraclough 8y agoWhy are you being obtuse, rather than trying to be clear? RISC-V is the major Free and Open CPU. RISC-V can run on FPGA. It's natural to want a comparison of this project against RISC-V, especially considering the write-up mentions the less successful OpenRISC project.
- monocasa 8y agoThis page appears to have been written in summer of 2016. Back then RISC-V didn't even have a stable privileged instruction set yet, so there wasn't really a RISC-V to compare it to in a meaningful sense.
- zipcpu 8y agoThe specification actually mentions RISC-V, and why I didn't use it. In hind sight, it's harder to decode the RISC-V instruction set than the one for the ZipCPU--to many holes in strange places.
- scottlamb 8y agoWhere does it mention RISC-V? I'm curious to read it. I hit ctrl-F to search for RISC-V in https://github.com/ZipCPU/zipcpu/blob/master/doc/spec.pdf https://github.com/ZipCPU/zipcpu/blob/master/doc/spec.pdf and only found a brief mention under "2.2.7: Operand B".
- zipcpu 8y agoCheck out page ix in the preface.