gcc/libgo
Ian Lance Taylor 7480a39b77 runtime: Use _mm_pause rather than __builtin_ia32_pause.
Based on a patch from Peter Collingbourne.

From-SVN: r211081
2014-05-30 13:53:58 +00:00
..
config
go gofrontend: deduplicate C syscall function declarations 2014-04-17 23:39:23 +00:00
runtime runtime: Use _mm_pause rather than __builtin_ia32_pause. 2014-05-30 13:53:58 +00:00
testsuite runtime: add the --without-libatomic configure option 2014-05-29 20:22:27 +00:00
aclocal.m4
config.h.in mksysinfo: Define CLONE flags. 2014-05-07 21:48:29 +00:00
configure runtime: add the --without-libatomic configure option 2014-05-29 20:22:27 +00:00
configure.ac runtime: add the --without-libatomic configure option 2014-05-29 20:22:27 +00:00
godeps.sh
LICENSE
Makefile.am runtime: add the --without-libatomic configure option 2014-05-29 20:22:27 +00:00
Makefile.in runtime: add the --without-libatomic configure option 2014-05-29 20:22:27 +00:00
MERGE libgo: Update to Go 1.2.1 release. 2014-03-03 20:14:52 +00:00
merge.sh
mksysinfo.sh mksysinfo: Define some more non-trivial TIOC constants. 2014-05-07 22:22:29 +00:00
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.