blob: a39d524df96d309f51d2cd08cebb5cd026edbe0d [file] [log] [blame]
See ../README.
This is the runtime support library for the Go programming language.
This library is intended for use with the Go frontend.
This library should not be stripped when it is installed. Go code
relies on being able to look up file/line information, which comes
from the debugging info using the libbacktrace library.
The library has only been tested on GNU/Linux using glibc, and on
Solaris. It should not be difficult to port to other operating
A copy of the Go library from, with several
changes for gccgo.
Runtime functions, written in C, which are called directly by the
compiler or by the library.
To contribute patches to the files in this directory, please see .
The master copy of these files is hosted at . 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 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.
This describes how to test libgo when built as part of gccgo.
To test a specific package, cd to the libgo build directory
(TARGET/libgo) and run `make PKG/check`. For example, `make
To see the exact commands that it runs, including how the compiler is
invoked, run `make GOTESTFLAGS=--trace bytes/check`. This will
display the commands if the test fails. If the test passes, the
commands and other output will be visible in a file named
check-testlog in a subdirectory with the name of the package being
checked. In the case of bytes/check, this will create
To leave the test program behind, run `make GOTESTFLAGS=--keep
bytes/check`. That will leave a gotestNNNN/test directory in the
libgo build directory. In that directory you can run
`LD_LIBRARY_PATH=../../.libs ./a.out -test.short` to run the tests.
You can run specific failing tests using a option. You can
see the tests being run with the -test.v option. You can run the
program under a debugger such as gdb.