gcc/libsanitizer
Kostya Serebryany 409f3b4663 libsanitizer: fix build on Mac 10.6
From-SVN: r206113
2013-12-19 12:54:11 +00:00
..
asan libsanitizer merge from upstream r196489 2013-12-05 10:28:59 +00:00
include/sanitizer libsanitizer merge from upstream r196489 2013-12-05 10:28:59 +00:00
interception libsanitizer merge from upstream r196090 2013-12-05 09:18:38 +00:00
lsan libsanitizer merge from upstream r196090 2013-12-05 09:18:38 +00:00
sanitizer_common libsanitizer: fix build on Mac 10.6 2013-12-19 12:54:11 +00:00
tsan libsanitizer merge from upstream r196489 2013-12-05 10:28:59 +00:00
ubsan libsanitizer merge from upstream r196090 2013-12-05 09:18:38 +00:00
acinclude.m4
aclocal.m4
ChangeLog libsanitizer: fix build on Mac 10.6 2013-12-19 12:54:11 +00:00
configure Add -lm to link_sanitizer_common 2013-12-05 06:41:38 -08:00
configure.ac Add -lm to link_sanitizer_common 2013-12-05 06:41:38 -08:00
configure.tgt re PR sanitizer/59061 (Port leaksanitizer) 2013-11-22 22:13:08 +01:00
libsanitizer.spec.in re PR sanitizer/59063 (ASAN: segfault in __interceptor_clock_gettime) 2013-11-29 12:30:36 +00:00
libtool-version
LICENSE.TXT
Makefile.am re PR sanitizer/59368 (libsanitizer spec file installed in the wrong place) 2013-12-05 09:56:03 +00:00
Makefile.in re PR sanitizer/59368 (libsanitizer spec file installed in the wrong place) 2013-12-05 09:56:03 +00:00
MERGE libsanitizer merge from upstream r196489 2013-12-05 10:28:59 +00:00
merge.sh libsanitizer merge from upstream r196489 2013-12-05 10:28:59 +00:00
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

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.