c915a58145
PR sanitizer/59136 libsanitizer/ * sanitizer_common/Makefile.am (AM_CXXFLAGS): If LIBBACKTRACE_SUPPORTED add -DSANITIZER_LIBBACKTRACE and -I/-include flags. * lsan/Makefile.am (liblsan_la_LIBADD): Add libsanitizer_libbacktrace.la if LIBBACKTRACE_SUPPORTED. * tsan/Makefile.am (libtsan_la_LIBADD): Likewise. * ubsan/Makefile.am (libubsan_la_LIBADD): Likewise. * asan/Makefile.am (libasan_la_LIBADD): Likewise. * Makefile.am (SUBDIRS): If LIBBACKTRACE_SUPPORTED add libbacktrace. * README.gcc: Document that also lsan and ubsan are maintained in compiler-rt upstream. * libbacktrace/Makefile.am: New file. * libbacktrace/backtrace-rename.h: New file. * libbacktrace/backtrace-supported.h.in: New file. * libbacktrace/bridge.cc: New file. * configure.ac: Add tests needed for libbacktrace build within libsanitizer. * sanitizer_common/Makefile.in: Regenerated. * lsan/Makefile.in: Regenerated. * tsan/Makefile.in: Regenerated. * ubsan/Makefile.in: Regenerated. * libbacktrace/Makefile.in: Generated. * config.h.in: Regenerated. * configure: Regenerated. * Makefile.in: Regenerated. * interception/Makefile.in: Regenerated. * asan/Makefile.in: Regenerated. * aclocal.m4: Regenerated. testsuite/ * c-c++-common/asan/strip-path-prefix-1.c: Allow also the filename:line instead of (modulename+offset) form with stripped initial / from the filename. From-SVN: r206475
21 lines
885 B
Plaintext
21 lines
885 B
Plaintext
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.
|