llvm-project/llgo/third_party/gofrontend/libgo
Andrew Wilkins d07b2b4228 [llgo] Disable known failing packages in check-libgo
Summary:
There are two packages in libgo which have
known failures when running the "make check" rule.
This change disables those packages in the tests so
that we can run libgo tests without them until the
root causes are identified and resolved.

Test Plan: ran check-libgo rule

Reviewers: pcc

Reviewed By: pcc

Subscribers: llvm-commits

Differential Revision: http://reviews.llvm.org/D8003

llvm-svn: 231448
2015-03-06 02:49:07 +00:00
..
config
go Roll gofrontend to 0fde0b6a7eb2 2015-02-13 22:59:07 +00:00
runtime Roll gofrontend to 0fde0b6a7eb2 2015-02-13 22:59:07 +00:00
testsuite
LICENSE
MERGE
Makefile.am [llgo] Disable known failing packages in check-libgo 2015-03-06 02:49:07 +00:00
Makefile.in [llgo] Disable known failing packages in check-libgo 2015-03-06 02:49:07 +00:00
PATENTS
README
README.gcc
aclocal.m4
config.h.in
configure
configure.ac
godeps.sh
merge.sh Roll gofrontend to 0fde0b6a7eb2 2015-02-13 22:59:07 +00:00
mksysinfo.sh
mvifdiff.sh

README

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.