gcc/libgo
Ian Lance Taylor 91d6f071fb runtime: Use a better heap location on arm64 systems.
Before this, the heap location used on a 64-bit system was not
available to user-space on arm64, so the "32-bit" strategy ended up
being used.  So use somewhere that is available, and for bonus points
is far away from where the kernel allocates address space by default.

From-SVN: r207977
2014-02-21 03:24:03 +00:00
..
config ltmain.sh: Patch for Solaris. 2014-02-03 17:39:44 +00:00
go re PR go/59430 (os/user FAILs on Solaris) 2014-01-08 01:08:29 +00:00
runtime runtime: Use a better heap location on arm64 systems. 2014-02-21 03:24:03 +00:00
testsuite
aclocal.m4
config.h.in
configure libgo/configure: Test for gold with gccgo -Wl,--help, not ld --help. 2014-01-22 19:10:47 +00:00
configure.ac libgo/configure: Test for gold with gccgo -Wl,--help, not ld --help. 2014-01-22 19:10:47 +00:00
godeps.sh
LICENSE
Makefile.am re PR go/59430 (os/user FAILs on Solaris) 2014-01-08 01:08:29 +00:00
Makefile.in re PR go/59430 (os/user FAILs on Solaris) 2014-01-08 01:08:29 +00:00
MERGE
merge.sh
mksysinfo.sh
PATENTS
README
README.gcc

See ../README.

This is the runtime support library for the Go programming language.
This library is intended for use with the Go frontend.

The library has only been tested on GNU/Linux using glibc.  It should
not be difficult to port to other operating systems.

The library has only been tested on x86/x86_64 systems.  It should not
be difficult to port to other architectures.

Directories:

go
  A copy of the Go library from http://golang.org/, with a few
  changes for gccgo.  Notably, the reflection interface is different.

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

syscalls
  System call support.

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.