Go compiler frontend (gccgo)
Go C++ Shell C Makefile Python Other
Switch branches/tags
Nothing to show
Clone or download
thanm and ianlancetaylor libgo: uncomment trace.Stop() call in testing package
Fix up the testing package to insure that execution traces
work properly (e.g. "-test.trace=<XXX>" command line option). The
call to stop tracing and emit the output file was stubbed out.

Change-Id: I205789804c15eaa356658780a699275bf29a206b
Reviewed-on: https://go-review.googlesource.com/128275
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Latest commit 274c88d Aug 7, 2018


A Go frontend

Ian Lance Taylor
Last update 15 June 2014

This is a compiler frontend for the Go programming language
(http://golang.org/).  The frontend was originally developed at
Google, and was released in November 2009.  It was originally written
by Ian Lance Taylor <iant@golang.org>.

It was originally written for GCC (http://gcc.gnu.org/).  As of this
writing it only supports GCC, but the GCC support has been separated
from the rest of the frontend, so supporting another compiler is

The go subdirectory holds the frontend source code.  This is mirrored
to the gcc/go subdirectory in the GCC repository.

The libgo subdirectory holds the library source code.  This is a copy
of the main Go library with various changes appropriate for this
compiler.  The main Go library is hosted at
http://go.googlesource.com/go, in the src directory.  The libgo
subdirectory is mirrored to the libgo subdirectory in the gcc

Legal Matters

To contribute patches to the files in this directory, please see
http://golang.org/doc/gccgo_contribute.html .

The master copy of these files is hosted at
http://go.googlesource.com/gofrontend (there is a mirror at
http://github.com/golang/gofrontend).  Changes to these files require
signing a Google contributor license agreement.  If you are the
copyright holder, you will need to agree to the individual contributor
license agreement at
http://code.google.com/legal/individual-cla-v1.0.html.  This agreement
can be completed online.

If your organization is the copyright holder, the organization will
need to agree to the corporate contributor license agreement at

If the copyright holder for your code has already completed the
agreement in connection with another Google open source project, it
does not need to be completed again.

The authors of these files may be found in the AUTHORS and