gcc/libsanitizer
GCC Administrator 58f8750342 Daily bump.
2021-08-12 00:16:28 +00:00
..
asan libsanitizer: Bump asan/tsan versions 2021-07-20 14:21:52 -07:00
builtins libsanitizer: merge from master 2021-05-13 09:29:17 +02:00
hwasan libsanitizer: Merge with upstream 2021-07-20 14:21:51 -07:00
include libsanitizer: Merge with upstream 2021-07-20 14:21:51 -07:00
interception libsanitizer: Merge with upstream 2021-07-20 14:21:51 -07:00
libbacktrace
lsan libsanitizer: Merge with upstream 2021-07-20 14:21:51 -07:00
sanitizer_common sanitizer: Cherry-pick realpath fix 2021-08-11 10:23:34 +02:00
tsan libsanitizer: Bump asan/tsan versions 2021-07-20 14:21:52 -07:00
ubsan libsanitizer: Apply local patches 2021-07-20 14:21:51 -07:00
acinclude.m4
aclocal.m4
ChangeLog Daily bump. 2021-08-12 00:16:28 +00:00
config.h.in
configure Update GNU/Hurd configure support 2021-01-05 16:04:14 -07:00
configure.ac libsanitizer: Only build libhwasan when targeting AArch64 2020-11-25 16:35:35 +00:00
configure.tgt Fix bashism in `libsanitizer/configure.tgt' 2021-08-03 13:24:47 +02:00
HOWTO_MERGE
libsanitizer.spec.in
LICENSE.TXT
LOCAL_PATCHES libsanitizer: Update LOCAL_PATCHES 2021-07-20 14:21:52 -07:00
Makefile.am libsanitizer: Only build libhwasan when targeting AArch64 2020-11-25 16:35:35 +00:00
Makefile.in libsanitizer: Only build libhwasan when targeting AArch64 2020-11-25 16:35:35 +00:00
MERGE libsanitizer: Merge with upstream 2021-07-20 14:21:51 -07:00
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.