riscv-gnu-toolchain VS kendryte-standalone-sdk

> 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?

I then looked at the .cargo/config.toml provided by the guide and saw that it wasn't actually statically compiling the code. After a bit of tinkering and building my own toolchain from here, I ended up with this config.toml file:

b) collabriscv - essentially gcc 12.2 + binutils master/2.40 as per https://github.com/riscv-collab/riscv-gnu-toolchain

Or would it be better to take what is in https://github.com/riscv-collab/riscv-gnu-toolchain which is gcc 12.2 and start from there?

I'm not able to build https://github.com/riscv-collab/riscv-gnu-toolchain.git like this:

Here is link number 1 - Previous text "SDK"

What is happening with Canaan and K210? They stopped developing the FreeRTOS SDK. Last release for the Standalone SDK was in 2019. Documentation is almost nonexistent.

See kpu_conv2d() in https://github.com/kendryte/kendryte-standalone-sdk/blob/develop/lib/nncase/include/kernels/k210/k210_kernels.h for a SW implementation of the KPU.