Re:Gollvm from Google
by ndesaulniers on Saturday May 27, 2017 @05:43PM
(#14432104)
But go ir != llvm ir. The idea is you can leave behind optimizations passes and backend, simply maintaining a frontend, when you adopt the llvm ir and toolchain.
[ Parent
| on HN ]
I don't disagree, but this is a different problem than the one cited above.
well, it is - because the existing architectural backends for llvm ir won't work with go's ir.
The cited problem was abstracting over different architectures. Go's IR solves this problem already. Solving this problem has nothing to do with making LLVM IR and Go's IR interoperable. A related problem might be that Go's IR doesn't target as many platforms as LLVM's, but that's still a different problem.