3 ms·
the risc-v privileged spec was the first time i looked at a page table structure and thought 'hey, writing a protected-memory operating system doesn't really so
by kragen 3y ago
the risc-v privileged spec was the first time i looked at a page table structure and thought 'hey, writing a protected-memory operating system doesn't really sound that hard' — though admittedly i haven't done it yet
also though rv32i is a pretty nice assembly language, though not quite as nice as arm32. what would be just about perfect would be arm32 with compare-and-branch instructions instead of condition codes, and modeless rv32c-style compressed instructions instead of a whole separate decoder mode that's full of easy ways to confuse your disassembler
also, a lot of companies and individuals are doing experimentation with the isa that arm licenses didn't allow them to do
there's no arm equivalent to the ch32v003 or serv or even picorv32. picorv32 means you can run linux on an fpga, and it's tantalizingly close to being supported with a fully free toolchain
it would be cool if you could write an assembly-language program on a ch32v003 and run it on a supercomputer, but that probably won't be a useful thing to do in practice; rv32 and rv64 are incompatible enough to be problematic, and cramping your code to fit into 16 registers will compromise its performance on your supercomputer, not to mention not using isa extensions like v. and if you don't care about its performance on your supercomputer you might as well just use qemu