Retro68/gcc/libsanitizer
2014-09-21 19:33:12 +02:00
..
asan upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
include upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
interception upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
libbacktrace upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
lsan upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
sanitizer_common upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
tsan upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
ubsan upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
acinclude.m4 upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
aclocal.m4 upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
ChangeLog upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
config.h.in upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
configure upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
configure.ac upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
configure.tgt upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
libsanitizer.spec.in upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
libtool-version upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
LICENSE.TXT upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
Makefile.am upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
Makefile.in upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
MERGE upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
merge.sh upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02:00
README.gcc upgrade to gcc 4.9.1 2014-09-21 19:33:12 +02: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
  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.