gcc/libsanitizer
Yury Gribov 4a7eaf5f94 re PR sanitizer/57316 (build failure in libsanitizer)
2014-01-23  Yury Gribov  <y.gribov@samsung.com>
	    Jakub Jelinek  <jakub@redhat.com>

	PR sanitizer/57316
	* configure.ac: Check for missing syscalls.
	* Makefile.am: Likewise.
	* configure: Regenerate.
	* Makefile.in: Regenerate.

Co-Authored-By: Jakub Jelinek <jakub@redhat.com>

From-SVN: r206966
2014-01-23 14:32:05 +00:00
..
asan
include
interception
libbacktrace
lsan
sanitizer_common
tsan
ubsan
acinclude.m4
aclocal.m4
ChangeLog re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
config.h.in
configure re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
configure.ac re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
configure.tgt
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
Makefile.in re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
MERGE
merge.sh
README.gcc

AddressSanitizer (http://code.google.com/p/address-sanitizer) and
ThreadSanitizer (http://code.google.com/p/thread-sanitizer/) are
projects initially developed by Google Inc.
Both tools consist of a compiler module and a run-time library.
The sources of the run-time library for these projects are hosted at
http://llvm.org/svn/llvm-project/compiler-rt in the following directories:
  include/sanitizer
  lib/sanitizer_common
  lib/interception
  lib/asan
  lib/tsan
  lib/lsan
  lib/ubsan

Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the
GCC tree.  All non-trivial changes, functionality improvements, etc. should go
through the upstream tree first and then be merged back to the GCC tree.
The merges from upstream should be done with the aid of the merge.sh script;
it will also update the file MERGE to contain the upstream revision
we merged with.