buildtools/gcc/libsanitizer
Augustin Cavalier b0a6bed08c Import GCC 8.3.
2019-05-23 17:48:23 -04:00
..
asan Import GCC 8.3. 2019-05-23 17:48:23 -04:00
builtins Import GCC 8.3. 2019-05-23 17:48:23 -04:00
include Import GCC 8.3. 2019-05-23 17:48:23 -04:00
interception Import GCC 8.3. 2019-05-23 17:48:23 -04:00
libbacktrace Import GCC 8.3. 2019-05-23 17:48:23 -04:00
lsan Import GCC 8.3. 2019-05-23 17:48:23 -04:00
sanitizer_common Import GCC 8.3. 2019-05-23 17:48:23 -04:00
tsan Import GCC 8.3. 2019-05-23 17:48:23 -04:00
ubsan Import GCC 8.3. 2019-05-23 17:48:23 -04:00
acinclude.m4 Import GCC 8.3. 2019-05-23 17:48:23 -04:00
aclocal.m4 import gcc 7.3.0 2018-03-19 15:34:23 -05:00
ChangeLog Import GCC 8.3. 2019-05-23 17:48:23 -04:00
config.h.in import gcc 5.3.0 2016-02-29 10:41:25 +01:00
configure Import GCC 8.3. 2019-05-23 17:48:23 -04:00
configure.ac Import GCC 8.3. 2019-05-23 17:48:23 -04:00
configure.tgt import gcc 7.3.0 2018-03-19 15:34:23 -05:00
HOWTO_MERGE import gcc 7.3.0 2018-03-19 15:34:23 -05:00
libsanitizer.spec.in import gcc 5.3.0 2016-02-29 10:41:25 +01:00
libtool-version import gcc 4.8.1 2013-06-05 18:35:38 +02:00
LICENSE.TXT import gcc 4.8.1 2013-06-05 18:35:38 +02:00
LOCAL_PATCHES import gcc 7.3.0 2018-03-19 15:34:23 -05:00
Makefile.am Import GCC 8.3. 2019-05-23 17:48:23 -04:00
Makefile.in Import GCC 8.3. 2019-05-23 17:48:23 -04:00
MERGE Import GCC 8.3. 2019-05-23 17:48:23 -04:00
merge.sh import gcc 7.3.0 2018-03-19 15:34:23 -05:00
README.gcc import gcc 5.3.0 2016-02-29 10:41:25 +01:00

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.