Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 07-May-2022 | - | ||||
asan/ | H | 03-May-2022 | - | 10,639 | 7,824 | |
include/ | H | 16-May-2018 | - | 4,063 | 3,491 | |
interception/ | H | 16-May-2018 | - | 1,377 | 959 | |
libbacktrace/ | H | 16-May-2018 | - | 1,014 | 776 | |
lsan/ | H | 16-May-2018 | - | 2,822 | 2,183 | |
sanitizer_common/ | H | 16-May-2018 | - | 32,730 | 26,175 | |
tsan/ | H | 16-May-2018 | - | 15,536 | 12,067 | |
ubsan/ | H | 16-May-2018 | - | 3,342 | 2,403 | |
ChangeLog | H A D | 07-Sep-2017 | 40.2 KiB | 1,246 | 953 | |
HOWTO_MERGE | H A D | 23-Oct-2015 | 2.5 KiB | 40 | 38 | |
MERGE | H A D | 23-Nov-2015 | 122 | 5 | 3 | |
Makefile.am | H A D | 14-May-2014 | 1.9 KiB | 73 | 58 | |
Makefile.in | H A D | 16-May-2018 | 23 KiB | 729 | 638 | |
README.gcc | H A D | 09-Jan-2014 | 885 | 21 | 19 | |
acinclude.m4 | H A D | 14-Nov-2012 | 389 | 11 | 9 | |
aclocal.m4 | H A D | 16-May-2018 | 36.4 KiB | 1,025 | 919 | |
config.h.in | H A D | 13-Apr-2015 | 3.9 KiB | 158 | 111 | |
configure | H A D | 16-May-2018 | 580.7 KiB | 19,664 | 16,495 | |
configure.ac | H A D | 14-Jan-2016 | 11.5 KiB | 404 | 352 | |
configure.tgt | H A D | 23-Nov-2015 | 1.5 KiB | 51 | 47 | |
libsanitizer.spec.in | H A D | 29-Nov-2013 | 275 | 12 | 6 | |
libtool-version | H A D | 12-Nov-2012 | 253 | 7 | 6 | |
merge.sh | H A D | 05-Dec-2013 | 1.9 KiB | 84 | 59 |
README.gcc
1AddressSanitizer (http://code.google.com/p/address-sanitizer) and 2ThreadSanitizer (http://code.google.com/p/thread-sanitizer/) are 3projects initially developed by Google Inc. 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 6http://llvm.org/svn/llvm-project/compiler-rt in the following directories: 7 include/sanitizer 8 lib/sanitizer_common 9 lib/interception 10 lib/asan 11 lib/tsan 12 lib/lsan 13 lib/ubsan 14 15Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the 16GCC tree. All non-trivial changes, functionality improvements, etc. should go 17through the upstream tree first and then be merged back to the GCC tree. 18The merges from upstream should be done with the aid of the merge.sh script; 19it will also update the file MERGE to contain the upstream revision 20we merged with. 21