gcc/libgo
Ian Lance Taylor a8ebf991f3 runtime: don't check for stale runtime
The gccgo runtime is never stale, and on a system with gc sources in
    ~/go the test may wind up checking whether the gc runtime is stale.
    
    Reviewed-on: https://go-review.googlesource.com/102282

From-SVN: r258865
2018-03-26 19:29:27 +00:00
..
config
go runtime: don't check for stale runtime 2018-03-26 19:29:27 +00:00
misc/cgo
runtime runtime: use a fence instruction before rdtsc 2018-03-07 14:31:03 +00:00
testsuite
aclocal.m4
config.h.in
configure
configure.ac
goarch.sh
godeps.sh
libgo.imp
LICENSE
Makefile.am libgo: add runtime/pprof/internal/profile.gox to noinst_DATA 2018-03-16 19:01:40 +00:00
Makefile.in libgo: add runtime/pprof/internal/profile.gox to noinst_DATA 2018-03-16 19:01:40 +00:00
match.sh
MERGE libgo: update to final Go 1.10 release 2018-02-28 01:19:07 +00:00
merge.sh
mkrsysinfo.sh
mksigtab.sh
mksysinfo.sh libgo: fix typo in mksysinfo.sh script 2018-03-05 18:44:44 +00:00
mvifdiff.sh
PATENTS
README
README.gcc
sysinfo.c
VERSION libgo: update to final Go 1.10 release 2018-02-28 01:19:07 +00:00

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
systems.

Directories:

go
  A copy of the Go library from http://golang.org/, with several
  changes for gccgo.

runtime
  Runtime functions, written in C, which are called directly by the
  compiler or by the library.

Contributing
============

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://code.google.com/p/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
http://code.google.com/legal/corporate-cla-v1.0.html.

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.