gcc/libsanitizer at 77a40ec16aeae9e13a96cef15799dd992cd23106 - gcc

History

Yury Gribov 2675305b4f re PR sanitizer/61100 (asan/tsan should have the sanitizer includes) 2014-05-14 Yury Gribov <y.gribov@samsung.com> PR sanitizer/61100 * Makefile.am (nodist_saninclude_HEADERS): Install public headers. * Makefile.in: Regenerate. * c-c++-common/asan/asan-interface-1.c: New test. * lib/asan-dg.exp (asan_include_flags): New function. (asan_init): Call asan_include_flags to obtain path to sanitizer headers. From-SVN: r210413		2014-05-14 08:33:45 +00:00
..
asan
include
interception
libbacktrace
lsan
sanitizer_common
tsan
ubsan
acinclude.m4
aclocal.m4
ChangeLog	re PR sanitizer/61100 (asan/tsan should have the sanitizer includes)	2014-05-14 08:33:45 +00:00
config.h.in
configure
configure.ac
configure.tgt
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am	re PR sanitizer/61100 (asan/tsan should have the sanitizer includes)	2014-05-14 08:33:45 +00:00
Makefile.in	re PR sanitizer/61100 (asan/tsan should have the sanitizer includes)	2014-05-14 08:33:45 +00:00
MERGE
merge.sh
README.gcc

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.