gcc/libsanitizer
2018-01-25 08:17:27 +00:00
..
asan re PR other/79046 (g++ -print-file-name=plugin uses full version number in path) 2017-01-21 09:47:11 +01:00
builtins
include backport: ptrace.h: New file. 2017-09-07 22:24:36 +02:00
interception re PR other/79046 (g++ -print-file-name=plugin uses full version number in path) 2017-01-21 09:47:11 +01:00
libbacktrace
lsan re PR sanitizer/82595 (bootstrap fails in libsanitizer on powerpc64-unknown-linux-gnu) 2017-10-20 10:01:31 +02:00
sanitizer_common backport: re PR sanitizer/81066 (sanitizer_stoptheworld_linux_libcdep.cc:276:22: error: aggregate ‘sigaltstack handler_stack’ has incomplete type and cannot be defined) 2017-07-17 21:41:08 +02:00
tsan backport: re PR sanitizer/81066 (sanitizer_stoptheworld_linux_libcdep.cc:276:22: error: aggregate ‘sigaltstack handler_stack’ has incomplete type and cannot be defined) 2017-07-17 21:41:08 +02:00
ubsan re PR other/79046 (g++ -print-file-name=plugin uses full version number in path) 2017-01-21 09:47:11 +01:00
acinclude.m4
aclocal.m4
ChangeLog Update ChangeLog and version files for release 2018-01-25 08:17:27 +00:00
config.h.in
configure
configure.ac
configure.tgt Add sanitizer_linux_x86_64.lo if __x86_64__ is defined by $CC 2017-10-05 03:45:04 -07:00
HOWTO_MERGE
libsanitizer.spec.in
libtool-version
LICENSE.TXT
LOCAL_PATCHES
Makefile.am
Makefile.in
MERGE
merge.sh re PR sanitizer/79168 (libtsan fails to link when cross compiling GCC tip for Aarch64 target) 2017-01-24 01:18:36 +01:00
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.