gcc/libgo
Ian Lance Taylor 14cda8a1cf libgo: separate mksysinfo inputs into separate Makefile targets
This is a step toward a version of mksysinfo that generates information
    for the runtime package.  This will be used to generate the
    runtime_sysinfo.go file, which is currently directly generated by a
    Makefile target.
    
    Reviewed-on: https://go-review.googlesource.com/29683

From-SVN: r240560
2016-09-27 21:32:50 +00:00
..
config
go internal/syscall/unix: add getrandom syscall for MIPS and SPARC 2016-09-23 21:00:43 +00:00
runtime
testsuite
aclocal.m4
config.h.in
configure
configure.ac
godeps.sh
LICENSE
Makefile.am libgo: separate mksysinfo inputs into separate Makefile targets 2016-09-27 21:32:50 +00:00
Makefile.in libgo: separate mksysinfo inputs into separate Makefile targets 2016-09-27 21:32:50 +00:00
match.sh
MERGE
merge.sh
mksysinfo.sh libgo: separate mksysinfo inputs into separate Makefile targets 2016-09-27 21:32:50 +00:00
mvifdiff.sh
PATENTS
README
README.gcc
sysinfo.c libgo: separate mksysinfo inputs into separate Makefile targets 2016-09-27 21:32:50 +00:00
VERSION

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.