riscv-gnu-toolchain

> no absurdely and grotesquely massive and complex compilers anywhere Absence of evidence is not evidence of absence, and anyway there's not even an absence: https://github.com/riscv-collab/riscv-gnu-toolchain https://llvm.org/docs/RISCVUsage.html > feature creeps on computer language syntax nowhere to be found At least one of us is very confused, and in case it's me, how do language details matter to RISC-V?

This is the standard RISC-V GNU toolchain top level repo that everyone has been using for nearly a decade. Nothing new here. (It was originally under github.com/riscv/riscv-gnu-toolchain, but was moved 2 or 3 years ago)

Damn dude. I never thought of that. So are you here right now declaring that RISC-V and all those companies are in the wrong and risc-v will be a disaster? Cause I might agree and be with you on that lol -Edit- I have no idea what the state of the compiler is https://github.com/riscv/riscv-gnu-toolchain > Warning: git clone takes around 6.65 GB of disk and download size WTF? If you're going that complex than... wtf?

The base RISC-V ISA is pretty simple, so you could learn it by writing your own emulator. I ended up writing one, and now I'm using it for scripting in game engines :) There are very few instructions for RV32I and RV64I - and you don't have to support both. Just pick one and implement the basic instructions. Then compile a cross-compiler from https://github.com/riscv/riscv-gnu-toolchain that is configured for either rv32i or rv64, like so: ./configure --prefix=$HOME/riscv --with-arch=rv32i make The toolchain repo is pretty big so make sure you do a shallow clone.

The vector extension is still in draft and still changing. We don't want to add support that we will have to remove later if the proposal changes again. But we have support in the rvv-intrinsic branch at github.com/riscv/riscv-gnu-toolchain. There is also LLVM work, they have different rules for development, so are handling this differently.

RISC-V has their own supported toolchain. You can get it here: https://github.com/riscv/riscv-gnu-toolchain.git With Rust, you can do what I did with my OS. It can compile out of the box. The kendryte has a "BSP" (base support package) that is essentially a minimal OS, but it is written in C.

Yes, when you build this: https://github.com/riscv/riscv-gnu-toolchain You can configure it with the extensions your system will support. The minimal is RV32I and RV64I. It will be full-length instructions which are easy to parse and no extras. ./configure --prefix=$HOME/riscv --with-arch=rv32i --with-abi=ilp32 I'm sure you can build a C standard library with these options as well, so you won't be as limited as you think. System calls are done through the ECALL instruction, and while it's mandatory, you don't really have to implement it.