gcc/libsanitizer
2015-02-27 07:46:30 -06:00
..
asan re PR bootstrap/63888 (bootstrap failed when configured with -with-build-config=bootstrap-asan --disable-werror) 2015-02-23 22:01:57 +01:00
include
interception Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +00:00
libbacktrace Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +00:00
lsan Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +00:00
sanitizer_common Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +00:00
tsan Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +00:00
ubsan Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +00:00
acinclude.m4
aclocal.m4
ChangeLog * configure.tgt: Enable build on powerpc*le-*-linux. 2015-02-27 07:46:30 -06:00
config.h.in
configure configure.ac: Move AM_ENABLE_MULTILIB before AC_PROG_CC. 2015-01-27 12:50:46 +00:00
configure.ac configure.ac: Move AM_ENABLE_MULTILIB before AC_PROG_CC. 2015-01-27 12:50:46 +00:00
configure.tgt * configure.tgt: Enable build on powerpc*le-*-linux. 2015-02-27 07:46:30 -06:00
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in Conditionally include target specific files while building TSAN 2015-01-25... 2015-01-23 11:53:04 +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.