4 ms·
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 toolchai
by ndesaulniers 9y ago
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.
- weberc2 9y agoI don't disagree, but this is a different problem than the one cited above.
- zeusk 9y agowell, it is - because the existing architectural backends for llvm ir won't work with go's ir.
- weberc2 9y agoThe 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.