What is the status of go-llvm and how is it relative to goc?

<ul> <li>How stable is it relative to goc (meaning, will your average golang program compile properly in go-llvm)?</li> <li>Does it generally produce faster executables?</li> </ul> <hr/>**评论：**<br/><br/>mewkiz: <pre><p>Similarly, it would be interesting with a comparison of gollvm <a href="https://go.googlesource.com/gollvm/" rel="nofollow">1</a> and go-llvm <a href="http://llvm.org/svn/llvm-project/llgo/trunk/README.TXT" rel="nofollow">2</a>.</p></pre>demonshreder: <pre><p>Was getting worried go-llvm has died. Nice to see gollvm. </p></pre>demonshreder: <pre><p>The gofrontend apparently still has GC issues as said in README here (<a href="https://github.com/golang/gofrontend/tree/master/go" rel="nofollow">https://github.com/golang/gofrontend/tree/master/go</a>). </p> <p>I haven&#39;t used llvm based Go but the other working compiler is gccgo:</p> <p>Based on this quite simplistic benchmark (<a href="https://github.com/slimsag/cgo-batching/blob/master/batched.go" rel="nofollow">https://github.com/slimsag/cgo-batching/blob/master/batched.go</a>), gccgo (v1.8 from GCC7) is 6 times slower than gc (v1.9) in executing Go code but is twice as fast in executing C code (cuz GCC).</p> <p>Edit: During my benchmark, gccgo didn&#39;t compile with ./vendor present.</p></pre>allowthere: <pre><blockquote> <p>gofrontend</p> </blockquote> <p>What&#39;s that?</p></pre>