3 ms·
well, it is - because the existing architectural backends for llvm ir won't work with go's ir.
by zeusk 9y ago
well, 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.