4 ms·

Github: https://github.com/riscv/riscv-angel https://github.com/riscv/riscv-angel jor1k has som RISV-V support now too, I wonder why that was done if this was

Github: https://github.com/riscv/riscv-angel https://github.com/riscv/riscv-angel jor1k has som RISV-V support now too, I wonder why that was done if this was in the works.

s-macke 11y ago
The RISC-V port in jor1k supports only 32-Bit whereas Angel supports only 64-Bit. Also jor1k supports the newest privilege instruction API whereas Angel hasn't been updated yet. Especially the jor1k port is assembler optimized by looking at the code the Javascript engines produce. I get up to 120 MIPS. But a comparison with Angel is unfair, because Javascript doesn't support 64-Bit yet. From my side the main idea is support the number of MMIO devices with virtio, framebuffer, network, sound and so on. Unfortunately the device support is still in an unfinished state and I don't know where RISC-V will go in the future. So at the moment you get just a dumb terminal and block device, which is pretty useless. There are also other reasons. The RISC-V project is more active currently than OpenRISC. So I hope to get finally a real distribution running with package management. There is still no native gdb for OpenRISC for example. But for RISC-V I know, that someone develops it. The same is true for other software.