I don't think you're forced to do it a certain way. The most mature RISC-V toolchain is the GNU toolchain, which is binutils + GCC + glibc/newlib/musl. Clang, G

I don't think you're forced to do it a certain way. The most mature RISC-V toolchain is the GNU toolchain, which is binutils + GCC + glibc/newlib/musl. Clang, GCC and all the libc's which are the foundation of most everything else have the assumption that you have one stack. It gets worse when you consider that modern languages often depend on glibc too. Example: https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kernel-requirements.html https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kerne... But, you can always go the golang route of depending on nothing but yourself. Then you get to decide!