The Go frontend is nearly ready to merge to mainline. It is pending approval of these patches to the build machinery:
Set poststage1_ldflags for all builds: http://gcc.gnu.org/ml/gcc-patches/2010-11/msg01639.html Add Go support to top level configure/make: http://gcc.gnu.org/ml/gcc-patches/2010-11/msg01963.html Add Go support to config-ml.in: http://gcc.gnu.org/ml/gcc-patches/2010-11/msg02033.html Joseph Myers has reviewed the code in gcc/go. Ralf Wildenhaus has reviewed the libgo Makefile.am and configure.ac. I believe that I have addressed all comments I've seen so far about the merge. The only possibly outstanding one that I can find regards the coding conventions. The intent of the code is to follow the conventions at http://gcc.gnu.org/wiki/CppConventions , though those have admittedly not been finalized, except that no space is used between a function name and a left parenthesis. If anybody would care to review the rest of the libgo directory outside of the libgo/go subdirectory, that would be helpful. Besides the new gcc/go and libgo directories, there are also three new files in gcc/testsuite/lib: go.exp, go-torture.exp, and go-dg.exp, and there are three new directories in gcc/testsuite: go.go-torture, go.dg, and go.test. I don't plan to send out any more individual patches for approval. My plan is to commit the rest of the Go code to mainline shortly after the above three build machinery patches are approved. Please let me know if you have any objections to this plan. Ian