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.