14 ms·
That's pretty cool! If you want something now, I've also written and abandoned this: https://github.com/aykevl/tinygo-gccgo https://github.com/aykevl/tinygo-gc
by aykevl 8y ago
That's pretty cool!
If you want something now, I've also written and abandoned this: https://github.com/aykevl/tinygo-gccgo https://github.com/aykevl/tinygo-gccgo
It actually worked fairly well, but the code was way too bloated to be useful.
- jsolson 8y agoHonestly for what I'm doing what you have here is a pretty reasonable start. I'm comfortable writing (and calling into) C where the Go bits aren't in place yet, and I'm a lot more familiar with LLVM's internals than with GCC's if I need to debug something. We'll see what I get up to after brunch. One request: if you're open to PRs (I can't promise I'll send any, but I'm trying to get into a habit of contributing to OSS with my hobby hackery), can you add a LICENSE file (context: the OSS patching policy I'm bound by is very friendly for projects on Github under most licenses -- https://opensource.google.com/docs/patching/ https://opensource.google.com/docs/patching/ -- it's more problematic when the license for the code is undefined)?
- aykevl 8y agoI'm certainly open to PRs :) Good catch on the LICENSE file, I totally forgot about it. I've added it now.