gcc/libsanitizer
GCC Administrator 4d68c7f7b5 Daily bump.
2023-05-01 00:16:44 +00:00
..
asan libsanitizer: Apply local patches 2023-04-30 09:38:32 +02:00
builtins libsanitizer: merge from upstream (3185e47b5a8444e9fd). 2023-04-26 15:51:56 +02:00
hwasan libsanitizer: link hwasan against lsan library 2023-04-30 21:31:49 +02:00
include libsanitizer: merge from upstream (3185e47b5a8444e9fd). 2023-04-26 15:51:56 +02:00
interception libsanitizer: merge from upstream (3185e47b5a8444e9fd). 2023-04-26 15:51:56 +02:00
libbacktrace
lsan libsanitizer: merge from upstream (3185e47b5a8444e9fd). 2023-04-26 15:51:56 +02:00
sanitizer_common libsanitizer: Apply local patches 2023-04-30 09:38:32 +02:00
tsan libsanitizer: Apply local patches 2023-04-30 09:38:32 +02:00
ubsan libsanitizer: Apply local patches 2023-04-30 09:38:32 +02:00
acinclude.m4
aclocal.m4
ChangeLog Daily bump. 2023-05-01 00:16:44 +00:00
config.h.in
configure libsanitizer: Regenerate configure 2023-01-31 10:35:33 +01:00
configure.ac libsanitizer/mips: always build with largefile support 2023-01-31 10:00:44 +08:00
configure.tgt libsanitizer, darwin: Unsupport Darwin >= 22 for now. 2023-04-18 07:27:48 +01:00
HOWTO_MERGE
libsanitizer.spec.in
LICENSE.TXT
LOCAL_PATCHES libsanitizer: update LOCAL_PATCHES revision 2023-04-30 09:56:46 +02:00
Makefile.am
Makefile.in
MERGE libsanitizer: merge from upstream (87e6e490e79384a5) 2023-04-30 09:38:14 +02: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.