gcc/libsanitizer
Kostya Serebryany c8e1377bf9 fix PR sanitizer/58994
From-SVN: r204838
2013-11-15 10:31:14 +00:00
..
asan fix PR sanitizer/58994 2013-11-15 10:31:14 +00:00
include/sanitizer libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
interception libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
lsan libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
sanitizer_common re PR sanitizer/59009 (libsanitizer merge from upstream r191666 breaks bootstrap on powerpc64-linux and aarch64-linux) 2013-11-13 16:34:33 -06:00
tsan libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
ubsan libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
acinclude.m4
aclocal.m4 Add libstdc++-raw-cxx.m4 and use it in libsanitizer 2012-12-11 13:32:11 -08:00
ChangeLog fix PR sanitizer/58994 2013-11-15 10:31:14 +00:00
configure libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
configure.ac libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
configure.tgt arm.c (arm_asan_shadow_offset): New function. 2013-05-07 16:17:50 +02:00
libtool-version
LICENSE.TXT
Makefile.am libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
Makefile.in libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
MERGE libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +00:00
merge.sh libsanitizer merge from upstream r191666 2013-11-04 21:33:31 +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.