Niels Nesse eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
..
asan eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
include eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
interception eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
libbacktrace eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
lsan eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
sanitizer_common eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
tsan eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
ubsan eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
ChangeLog eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
LICENSE.TXT eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
MERGE eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
Makefile.am eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
Makefile.in eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
README.gcc eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
acinclude.m4 eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
aclocal.m4 eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
config.h.in eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
configure eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
configure.ac eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
configure.tgt eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
libsanitizer.spec.in eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
libtool-version eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад
merge.sh eb72d50f44 Import gcc 5.2.0 from tarball 9 лет назад

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.