07:59 <sagar_acharya> I cannot build the riscv-gnu-toolchain.

08:00 <sagar_acharya> I don't like using pre-compiled binaries.

08:00 <sagar_acharya> Is there a way to use picorv32 without the riscv-gnu-toolchain ?

08:04 <tnt> ... how exactly do you want to use a RISC-V CPU if you don't have a RISC-V compiler ?

08:04 <tnt> I'm sure there are others than the gcc toolchain, you can try to build clang or buy a commercial compiler ...

08:10 <sagar_acharya> That is used to compile the programs to be put on picorv32 right? There must be other compilers.

08:12 <xiretza[m]> LLVM also has a RISC-V backend, but I don't know of any others.

08:13 <sagar_acharya> Alright, I will check it out. Thanks folks.

08:14 <xiretza[m]> RISC-V is a very recent development all things considered, people don't usually bother writing their own compiler for their new architecture anymore when GCC and LLVM exist

08:19 <sagar_acharya> True. I'll try to struggle compiling these own my own for a while then....

08:27 <sagar_acharya> https://repo.or.cz/tinycc.git/tree

08:27 <tpb> Title: Public Git Hosting - tinycc.git/tree (at repo.or.cz)

08:27 <sagar_acharya> This has support for riscv64

08:28 <xiretza[m]> what OS/distribution are you on?

08:28 <sagar_acharya> Hyperbola v0.4

08:29 <sagar_acharya> It uses gcc 8.4.0

08:32 <xiretza[m]> yeah they don't seem to repackage any of the RISC-V tooling from Arch

08:33 <xiretza[m]> you can try tinycc, but it's quite possible for deeply embedded firmware to require some GCC extension or another

08:37 <sagar_acharya> So tcc will work for picorv ?

08:38 <sagar_acharya> Can you please explain in a simpler way? I don't get deeply embedded firmware.

08:38 <sagar_acharya> I think picorv has rv32 and tcc has 64bit so it shouldn't work