gcc/libgo
Ian Lance Taylor 52c9cfeb08 runtime: install SIGURG handler on C created threads
Precise stack scan uses SIGURG to trigger a stack scan. We need
    to have Go signal handler installed for SIGURG.
    
    Reviewed-on: https://go-review.googlesource.com/c/159097

From-SVN: r268230
2019-01-24 05:31:14 +00:00
..
config
go runtime: install SIGURG handler on C created threads 2019-01-24 05:31:14 +00:00
misc/cgo
runtime libgo: fix building, and some testing, on Solaris 2019-01-21 23:05:52 +00:00
testsuite
aclocal.m4
check-packages.txt
config.h.in
configure
configure.ac
goarch.sh
godeps.sh
gotool-packages.txt
libgo-packages.txt
libgo.imp
LICENSE
Makefile.am libgo: fix building, and some testing, on Solaris 2019-01-21 23:05:52 +00:00
Makefile.in libgo: fix building, and some testing, on Solaris 2019-01-21 23:05:52 +00:00
match.sh
MERGE
merge.sh
mkrsysinfo.sh
mkruntimeinc.sh
mksigtab.sh
mksysinfo.sh
mvifdiff.sh
PATENTS
README
README.gcc
sysinfo.c
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.