gcc/libsanitizer
Maxim Ostapenko 02f4d3e9da Update HOWTO_MERGE file for libsanitizer.
From-SVN: r229215
2015-10-23 11:50:30 +03:00
..
asan re PR bootstrap/63888 (bootstrap failed when configured with -with-build-config=bootstrap-asan --disable-werror) 2015-10-21 10:47:54 +03:00
include libsanitizer merge from upstream r250806. 2015-10-21 10:32:45 +03:00
interception libsanitizer merge from upstream r250806. 2015-10-21 10:32:45 +03:00
libbacktrace
lsan libsanitizer merge from upstream r250806. 2015-10-21 10:32:45 +03:00
sanitizer_common sanitizer_stacktrace.cc (GetCanonicFrame): Assume we compiled code with GCC when extracting the caller PC for ARM if... 2015-10-21 10:51:03 +03:00
tsan libsanitizer merge from upstream r250806. 2015-10-21 10:32:45 +03:00
ubsan Fix bootstrap on x86_64-apple-darwin14 after r229119. 2015-10-22 12:47:17 +03:00
acinclude.m4
aclocal.m4
ChangeLog Fix bootstrap on x86_64-apple-darwin14 after r229119. 2015-10-22 12:47:17 +03:00
config.h.in
configure Fix bootstrap on x86_64-apple-darwin14 after r229119. 2015-10-22 12:47:17 +03:00
configure.ac Fix bootstrap on x86_64-apple-darwin14 after r229119. 2015-10-22 12:47:17 +03:00
configure.tgt libsanitizer merge from upstream r250806. 2015-10-21 10:32:45 +03:00
HOWTO_MERGE Update HOWTO_MERGE file for libsanitizer. 2015-10-23 11:50:30 +03:00
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in
MERGE libsanitizer merge from upstream r250806. 2015-10-21 10:32:45 +03: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.