NameDateSize

..06-Jun-201676

acinclude.m4H A D29-Jan-2014389

aclocal.m4H A D05-Mar-201636.1 KiB

asan/H06-Jun-201643

ChangeLogH A D06-Jun-201633.7 KiB

config.h.inH A D05-Mar-20163.9 KiB

configureH A D05-Mar-2016577.3 KiB

configure.acH A D05-Mar-201610.4 KiB

configure.tgtH A D05-Mar-20161.4 KiB

include/H05-Mar-20164

interception/H05-Mar-201612

libbacktrace/H05-Mar-20167

libsanitizer.spec.inH A D05-Mar-2016275

libtool-versionH A D29-Jan-2014253

LICENSE.TXTH A D29-Jan-20144.4 KiB

lsan/H05-Mar-201616

Makefile.amH A D05-Mar-20161.9 KiB

Makefile.inH A D05-Mar-201621.9 KiB

MERGEH A D05-Mar-2016122

merge.shH A D05-Mar-20161.9 KiB

README.gccH A D05-Mar-2016885

sanitizer_common/H06-Jun-201692

tsan/H05-Mar-201656

ubsan/H05-Mar-201619

README.gcc

1AddressSanitizer (http://code.google.com/p/address-sanitizer) and
2ThreadSanitizer (http://code.google.com/p/thread-sanitizer/) are
3projects initially developed by Google Inc.
4Both tools consist of a compiler module and a run-time library.
5The sources of the run-time library for these projects are hosted at
6http://llvm.org/svn/llvm-project/compiler-rt in the following directories:
7  include/sanitizer
8  lib/sanitizer_common
9  lib/interception
10  lib/asan
11  lib/tsan
12  lib/lsan
13  lib/ubsan
14
15Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the
16GCC tree.  All non-trivial changes, functionality improvements, etc. should go
17through the upstream tree first and then be merged back to the GCC tree.
18The merges from upstream should be done with the aid of the merge.sh script;
19it will also update the file MERGE to contain the upstream revision
20we merged with.
21