gcc/libsanitizer
2012-11-23 04:09:17 +00:00
..
asan configure.ac: Invoke AM_MAINTAINER_MODE. 2012-11-16 15:19:15 +00:00
include/sanitizer Define/use hardware pointer type for stack unwind 2012-11-16 04:02:29 -08:00
interception configure.ac: Invoke AM_MAINTAINER_MODE. 2012-11-16 15:19:15 +00:00
sanitizer_common Fix sanitizer build on sparc64. 2012-11-20 12:54:49 -08:00
tsan Makefile.am (AM_CXXFLAGS): Remove -Wno-variadic-macros. 2012-11-23 01:31:54 +01:00
acinclude.m4 Update configure.ac for GCC tree and remove unused files 2012-11-13 16:02:12 -08:00
aclocal.m4 configure.ac: Invoke AM_MAINTAINER_MODE. 2012-11-16 15:19:15 +00:00
ChangeLog [libsanitizer] a script to help merging asan/tsan from upstream 2012-11-23 04:09:17 +00:00
configure Makefile.am (AM_CXXFLAGS): Remove -Wno-variadic-macros. 2012-11-23 01:31:54 +01:00
configure.ac Makefile.am (AM_CXXFLAGS): Remove -Wno-variadic-macros. 2012-11-23 01:31:54 +01:00
configure.tgt Makefile.am (AM_CXXFLAGS): Remove -Wno-variadic-macros. 2012-11-23 01:31:54 +01:00
libtool-version
LICENSE.TXT
Makefile.am Makefile.am (AM_CXXFLAGS): Remove -Wno-variadic-macros. 2012-11-23 01:31:54 +01:00
Makefile.in Makefile.am (AM_CXXFLAGS): Remove -Wno-variadic-macros. 2012-11-23 01:31:54 +01:00
merge.sh [libsanitizer] a script to help merging asan/tsan from upstream 2012-11-23 04:09:17 +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.