gcc/libsanitizer
Martin Liska bdb9d47218 libsanitizer: update LOCAL_PATCHES. 2021-11-05 18:21:42 +01:00
..
asan libsanitizer: Apply local patches 2021-11-05 18:21:29 +01:00
builtins libsanitizer: merge from master 2021-05-13 09:29:17 +02:00
hwasan libsanitizer: merge from master (78d3e0a4f1406b17cdecc77540e09210670fe9a9). 2021-11-05 18:21:27 +01:00
include libsanitizer: Merge with upstream 2021-10-01 09:02:54 -07:00
interception libsanitizer: Add AM_CCASFLAGS to Makefile.am 2021-10-08 06:17:01 -07:00
libbacktrace
lsan libsanitizer: merge from master (c86b4503a94c277534ce4b9a5c015a6ac151b98a). 2021-11-04 13:24:53 +01:00
sanitizer_common libsanitizer: Apply local patches 2021-11-05 18:21:29 +01:00
tsan libsanitizer: Apply local patches 2021-11-05 18:21:29 +01:00
ubsan libsanitizer: Apply local patches 2021-11-05 18:21:29 +01:00
ChangeLog Daily bump. 2021-11-05 00:16:36 +00:00
HOWTO_MERGE
LICENSE.TXT
LOCAL_PATCHES libsanitizer: update LOCAL_PATCHES. 2021-11-05 18:21:42 +01:00
MERGE libsanitizer: merge from master (78d3e0a4f1406b17cdecc77540e09210670fe9a9). 2021-11-05 18:21:27 +01:00
Makefile.am
Makefile.in
README.gcc
acinclude.m4
aclocal.m4
config.h.in
configure lisanitizer: Apply autoreconf. 2021-11-04 13:26:05 +01:00
configure.ac
configure.tgt Fix bashism in `libsanitizer/configure.tgt' 2021-08-03 13:24:47 +02:00
libsanitizer.spec.in
merge.sh

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://github.com/llvm/llvm-project in the following directories:
  compiler-rt/include/sanitizer
  compiler-rt/lib/sanitizer_common
  compiler-rt/lib/interception
  compiler-rt/lib/asan
  compiler-rt/lib/tsan
  compiler-rt/lib/lsan
  compiler-rt/lib/ubsan
  compiler-rt/lib/hwasan

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.