gcc/libgo
Ian Lance Taylor bb3976df48 cmd/go, cmd/vet: make vet work with gccgo
Backport https://golang.org/cl/113715 and https://golang.org/cl/113716:
    
    cmd/go: don't pass -compiler flag to vet
    
    Without this running go vet -compiler=gccgo causes vet to fail.
    The vet tool does need to know the compiler, but it is passed in
    vetConfig.Compiler.
    
    cmd/go, cmd/vet, go/internal/gccgoimport: make vet work with gccgo
    
    When using gccgo/GoLLVM, there is no package file for a standard
    library package. Since it is impossible for the go tool to rebuild the
    package, and since the package file exists only in the form of a .gox
    file, this seems like the best choice. Unfortunately it was confusing
    vet, which wanted to see a real file. This caused vet to report errors
    about missing package files for standard library packages. The
    gccgoimporter knows how to correctly handle this case. Fix this by
    
    1) telling vet which packages are standard;
    2) letting vet skip those packages;
    3) letting the gccgoimporter handle this case.
    
    As a separate required fix, gccgo/GoLLVM has no runtime/cgo package,
    so don't try to depend on it (as it happens, this fixes golang/go#25324).
    
    The result is that the cmd/go vet tests pass when using -compiler=gccgo.
    
    Reviewed-on: https://go-review.googlesource.com/114516

From-SVN: r260913
2018-05-30 00:16:58 +00:00
..
config
go cmd/go, cmd/vet: make vet work with gccgo 2018-05-30 00:16:58 +00:00
misc/cgo re PR go/84484 (libgo configure tests fail to find -latomic) 2018-02-22 19:49:04 +00:00
runtime libgo: fix for unaligned read in go-unwind.c's read_encoded_value() 2018-05-04 14:29:05 +00:00
testsuite libgo: add support for the Nios II architecture 2018-05-02 22:28:46 +00:00
aclocal.m4
check-packages.txt libgo: refactor code to enumerate stdlib packages 2018-05-02 21:57:35 +00:00
config.h.in
configure libgo: add support for the Nios II architecture 2018-05-02 22:28:46 +00:00
configure.ac libgo: add support for the Nios II architecture 2018-05-02 22:28:46 +00:00
goarch.sh libgo: add support for the Nios II architecture 2018-05-02 22:28:46 +00:00
godeps.sh
gotool-packages.txt libgo: refactor code to enumerate stdlib packages 2018-05-02 21:57:35 +00:00
libgo-packages.txt libgo: refactor code to enumerate stdlib packages 2018-05-02 21:57:35 +00:00
libgo.imp
LICENSE
Makefile.am go/build, cmd/go: update to match recent changes to gc 2018-05-09 21:49:47 +00:00
Makefile.in go/build, cmd/go: update to match recent changes to gc 2018-05-09 21:49:47 +00:00
match.sh libgo: add support for the Nios II architecture 2018-05-02 22:28:46 +00:00
MERGE libgo: update to final Go 1.10 release 2018-02-28 01:19:07 +00:00
merge.sh
mkrsysinfo.sh
mkruntimeinc.sh libgo: refactor code to enumerate stdlib packages 2018-05-02 21:57:35 +00:00
mksigtab.sh
mksysinfo.sh libgo: add type/const references to sysinfo.c 2018-05-02 22:32:23 +00:00
mvifdiff.sh
PATENTS
README
README.gcc
sysinfo.c libgo: add type/const references to sysinfo.c 2018-05-02 22:32:23 +00:00
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.