Retro68/gcc/libsanitizer
2017-04-10 13:32:00 +02:00
..
asan upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
include upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
interception upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
libbacktrace upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
lsan upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
sanitizer_common upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
tsan upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
ubsan upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
acinclude.m4
aclocal.m4 upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
ChangeLog upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
config.h.in Update gcc to 5.2.0 2015-08-28 17:33:40 +02:00
configure upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
configure.ac upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
configure.tgt upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
HOWTO_MERGE upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am Update gcc to 5.2.0 2015-08-28 17:33:40 +02:00
Makefile.in upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
MERGE upgrade gcc to 6.3.0, binutils to 2.28 2017-04-10 13:32:00 +02:00
merge.sh
README.gcc

AddressSanitizer (http://code.google.com/p/address-sanitizer) and
ThreadSanitizer (http://code.google.com/p/thread-sanitizer/) 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
http://llvm.org/svn/llvm-project/compiler-rt in the following directories:
  include/sanitizer
  lib/sanitizer_common
  lib/interception
  lib/asan
  lib/tsan
  lib/lsan
  lib/ubsan

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.