gcc/libsanitizer
Jakub Jelinek f2798565b4 sanitizer_symbolizer_libbacktrace.cc, [...]: Cherry pick upstream r224308.
* sanitizer_common/sanitizer_symbolizer_libbacktrace.cc,
	sanitizer_common/sanitizer_symbolizer_libbacktrace.h,
	sanitizer_common/sanitizer_symbolizer_posix_libcdep.cc: Cherry pick
	upstream r224308.

From-SVN: r218778
2014-12-16 12:35:34 +01:00
..
asan Makefile.am (AM_CXXFLAGS): Use -std=gnu++11. 2014-11-14 15:23:51 +01:00
include libsanitizer merge from upstream r221802 2014-11-13 20:41:38 +00:00
interception Makefile.am (AM_CXXFLAGS): Use -std=gnu++11. 2014-11-14 15:23:51 +01:00
libbacktrace Makefile.am (AM_CXXFLAGS): Use -std=gnu++11. 2014-11-14 15:23:51 +01:00
lsan Makefile.am (AM_CXXFLAGS): Use -std=gnu++11. 2014-11-14 15:23:51 +01:00
sanitizer_common sanitizer_symbolizer_libbacktrace.cc, [...]: Cherry pick upstream r224308. 2014-12-16 12:35:34 +01:00
tsan Makefile.am (AM_CXXFLAGS): Use -std=gnu++11. 2014-11-14 15:23:51 +01:00
ubsan Makefile.am (AM_CXXFLAGS): Use -std=gnu++11. 2014-11-14 15:23:51 +01:00
acinclude.m4
aclocal.m4
ChangeLog sanitizer_symbolizer_libbacktrace.cc, [...]: Cherry pick upstream r224308. 2014-12-16 12:35:34 +01:00
config.h.in
configure Always use PIC option with -shared in libtool 2014-11-21 08:49:17 -08:00
configure.ac
configure.tgt
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in
MERGE libsanitizer merge from upstream r221802 2014-11-13 20:41:38 +00: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.