riscv-gnu-toolchain VS ipxe

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

Simplest version of what you are trying to do could be to use iPXE (ipxe.org)

https://github.com/ipxe/ipxe/issues/349 suggested implementing this solution: " The solution is to restore the TPL to the original one but not always set it to TPL_CALLBACK". I am not sure if this is applicable to my Dell Precision T5610 or is it something specific to iPXE.

Link: https://ipxe.org/

git clone https://github.com/ipxe/ipxe.git

So for instance on this file here https://github.com/ipxe/ipxe/blob/master/src/config/general.h it would turn this

Make use of that file. You will note that it doesn't actually exist in the repository you're looking at. The Makefile will create it if doesn't exist... but you can always create it yourself with your own content.