Niels Nesse
eb72d50f44
Import gcc 5.2.0 from tarball
|
9 éve | |
|---|---|---|
| .. | ||
| asan | 9 éve | |
| include | 9 éve | |
| interception | 9 éve | |
| libbacktrace | 9 éve | |
| lsan | 9 éve | |
| sanitizer_common | 9 éve | |
| tsan | 9 éve | |
| ubsan | 9 éve | |
| ChangeLog | 9 éve | |
| LICENSE.TXT | 9 éve | |
| MERGE | 9 éve | |
| Makefile.am | 9 éve | |
| Makefile.in | 9 éve | |
| README.gcc | 9 éve | |
| acinclude.m4 | 9 éve | |
| aclocal.m4 | 9 éve | |
| config.h.in | 9 éve | |
| configure | 9 éve | |
| configure.ac | 9 éve | |
| configure.tgt | 9 éve | |
| libsanitizer.spec.in | 9 éve | |
| libtool-version | 9 éve | |
| merge.sh | 9 éve | |
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.
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.