gcc/libsanitizer
GCC Administrator c3a4169be9 Daily bump. 2020-05-27 07:45:56 +00:00
..
asan Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
builtins
include
interception Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
libbacktrace Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
lsan Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
sanitizer_common libsanitizer: Add missing file and regen Makefile.in 2020-05-01 16:24:37 +02:00
tsan Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
ubsan Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
ChangeLog Daily bump. 2020-05-27 07:45:56 +00:00
HOWTO_MERGE
LICENSE.TXT
LOCAL_PATCHES Update merge.sh to reflect usage of git. 2020-05-26 08:48:14 +02:00
MERGE
Makefile.am
Makefile.in Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
README.gcc
acinclude.m4
aclocal.m4 Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
config.h.in
configure x86: Also check if -fcf-protection works 2020-05-15 09:07:17 -07:00
configure.ac Add `--with-toolexeclibdir=' configuration option 2020-01-24 11:24:25 +00:00
configure.tgt gcc: Enable bits for sanitizer support on FreeBSD x86_64 2020-05-01 17:18:47 +02:00
libsanitizer.spec.in
merge.sh Update merge.sh to reflect usage of git. 2020-05-26 08:48:14 +02:00

README.gcc

AddressSanitizer and ThreadSanitizer (https://github.com/google/sanitizers) 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
https://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.