Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 07-May-2022 | - | ||||
asan/ | H | 28-Jul-2021 | - | 15,129 | 11,085 | |
builtins/ | H | 28-Jul-2021 | - | 201 | 155 | |
hwasan/ | H | 28-Jul-2021 | - | 5,505 | 3,971 | |
include/ | H | 28-Jul-2021 | - | 9,913 | 8,520 | |
interception/ | H | 28-Jul-2021 | - | 2,357 | 1,640 | |
libbacktrace/ | H | 28-Jul-2021 | - | 1,121 | 874 | |
lsan/ | H | 28-Jul-2021 | - | 4,676 | 3,479 | |
sanitizer_common/ | H | 28-Jul-2021 | - | 63,852 | 52,333 | |
tsan/ | H | 28-Jul-2021 | - | 21,190 | 16,431 | |
ubsan/ | H | 28-Jul-2021 | - | 4,630 | 3,281 | |
ChangeLog | H A D | 28-Jul-2021 | 71.1 KiB | 2,218 | 1,673 | |
HOWTO_MERGE | H A D | 28-Jul-2021 | 2.8 KiB | 44 | 42 | |
LOCAL_PATCHES | H A D | 28-Jul-2021 | 82 | 3 | 2 | |
MERGE | H A D | 28-Jul-2021 | 156 | 5 | 3 | |
Makefile.am | H A D | 28-Jul-2021 | 2.1 KiB | 79 | 64 | |
Makefile.in | H A D | 28-Jul-2021 | 24.7 KiB | 793 | 693 | |
README.gcc | H A D | 28-Jul-2021 | 936 | 22 | 19 | |
acinclude.m4 | H A D | 28-Jul-2021 | 446 | 13 | 11 | |
aclocal.m4 | H A D | 28-Jul-2021 | 43.4 KiB | 1,203 | 1,093 | |
config.h.in | H A D | 28-Jul-2021 | 4 KiB | 164 | 115 | |
configure | H A D | 28-Jul-2021 | 592.1 KiB | 20,121 | 16,855 | |
configure.ac | H A D | 28-Jul-2021 | 11.7 KiB | 416 | 360 | |
configure.tgt | H A D | 28-Jul-2021 | 2.1 KiB | 78 | 74 | |
libsanitizer.spec.in | H A D | 28-Jul-2021 | 310 | 14 | 7 | |
merge.sh | H A D | 28-Jul-2021 | 2.1 KiB | 89 | 63 |
README.gcc
1AddressSanitizer and ThreadSanitizer (https://github.com/google/sanitizers) are 2projects initially developed by Google Inc. 3 4Both tools consist of a compiler module and a run-time library. 5The sources of the run-time library for these projects are hosted at 6https://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 16Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the 17GCC tree. All non-trivial changes, functionality improvements, etc. should go 18through the upstream tree first and then be merged back to the GCC tree. 19The merges from upstream should be done with the aid of the merge.sh script; 20it will also update the file MERGE to contain the upstream revision 21we merged with. 22