You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's is a bit of an unusual use-case--our team is building a zero-knowledge VM (zkVM) that proves the execution of the RISC-V32im instruction set: https://github.com/succinctlabs/sp1.
We use ecalls to do stdin and stdout into the zkVM environment, but other than that usually we just have pure golang code that is proving some sort of computation.
In that case, the zkVM would be the target. Especially since you say this:
We use ecalls to do stdin and stdout into the zkVM environment, [...]
This means that functions like putchar would call those kinds of syscalls. The runtime needs to know about these sorts of details, for example to print panic messages or to correctly schedule goroutines.
Also, the linker will need to know details like at which address it can be linked and which memory area it can use for the heap.
Is it possible to compile TinyGo to a RV32IM (RISC-V 32 bit) backend? I tried running
But got the following error on this very simple program:
The text was updated successfully, but these errors were encountered: