> The best thing about gccgo is that it is not burdened with the weirdness of golang's calling convention
Interesting. I saw go breaking from the c abi as the primary reason to use it; otherwise you might as well use java or rust.
Isn't that horribly out of date? More recent benchmarks elsewhere performed after some Go improvements show Go's C FFI having drastically lower overheard, by at least an order of magnitude, IIUC.
[0]: https://github.com/dyu/ffi-overhead