gcc/libsanitizer
Kostya Serebryany 2660d12d0a libsanitizer merge from upstream r173241
From-SVN: r195404
2013-01-23 11:41:33 +00:00
..
asan libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
include/sanitizer libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
interception libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
sanitizer_common libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
tsan libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
acinclude.m4 Update configure.ac for GCC tree and remove unused files 2012-11-13 16:02:12 -08:00
aclocal.m4 Add libstdc++-raw-cxx.m4 and use it in libsanitizer 2012-12-11 13:32:11 -08:00
ChangeLog libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
configure Remove "-I" from LIBSTDCXX_RAW_CXX_LDFLAGS 2013-01-07 10:23:42 -08:00
configure.ac Add libstdc++-raw-cxx.m4 and use it in libsanitizer 2012-12-11 13:32:11 -08:00
configure.tgt configure.tgt: Enable build on powerpc*-linux. 2012-12-06 15:53:36 -06:00
libtool-version
LICENSE.TXT
Makefile.am Restore AM_MAKEFLAGS in libsanitizer 2012-12-12 07:41:36 -08:00
Makefile.in Restore AM_MAKEFLAGS in libsanitizer 2012-12-12 07:41:36 -08:00
MERGE libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
merge.sh libsanitizer merge from upstream r173241 2013-01-23 11:41:33 +00:00
README.gcc [libsanitizer] a script to help merging asan/tsan from upstream 2012-11-23 04:09:17 +00:00

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.