Home | History | Annotate | only in /src/external/gpl3/gcc.old/dist/libsanitizer
Up to higher level directory
NameDateSize
acinclude.m419-Aug-2020446
aclocal.m407-Sep-202543.4K
asan/25-Feb-2026
builtins/25-Feb-2026
config.h.in09-Apr-20214K
configure07-Sep-2025593.7K
configure.ac07-Sep-202512K
configure.tgt07-Sep-20252.2K
HOWTO_MERGE07-Sep-20252.8K
hwasan/25-Feb-2026
include/25-Feb-2026
interception/25-Feb-2026
libbacktrace/25-Feb-2026
libsanitizer.spec.in07-Sep-2025310
LICENSE.TXT26-Sep-20194.4K
LOCAL_PATCHES07-Sep-202582
lsan/25-Feb-2026
Makefile.am07-Sep-20252.1K
Makefile.in07-Sep-202524.7K
MERGE07-Sep-2025156
merge.sh07-Sep-20252.1K
README.gcc07-Sep-2025936
sanitizer_common/25-Feb-2026
tsan/25-Feb-2026
ubsan/25-Feb-2026

README.gcc

      1 AddressSanitizer and ThreadSanitizer (https://github.com/google/sanitizers) are
      2 projects initially developed by Google Inc.
      3 
      4 Both tools consist of a compiler module and a run-time library.
      5 The sources of the run-time library for these projects are hosted at
      6 https://github.com/llvm/llvm-project in the following directories:
      7   compiler-rt/include/sanitizer
      8   compiler-rt/lib/sanitizer_common
      9   compiler-rt/lib/interception
     10   compiler-rt/lib/asan
     11   compiler-rt/lib/tsan
     12   compiler-rt/lib/lsan
     13   compiler-rt/lib/ubsan
     14   compiler-rt/lib/hwasan
     15 
     16 Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the
     17 GCC tree.  All non-trivial changes, functionality improvements, etc. should go
     18 through the upstream tree first and then be merged back to the GCC tree.
     19 The merges from upstream should be done with the aid of the merge.sh script;
     20 it will also update the file MERGE to contain the upstream revision
     21 we merged with.
     22