gcc/libsanitizer
Jakub Jelinek 69af4eecb8 re PR sanitizer/71160 (libasan: Backport support for malloc within dlsym)
PR sanitizer/71160
	* asan/asan_malloc_linux.cc: Cherry pick upstream r254395
	and r269633.

From-SVN: r236314
2016-05-17 11:17:54 +02:00
..
asan re PR sanitizer/71160 (libasan: Backport support for malloc within dlsym) 2016-05-17 11:17:54 +02:00
include Move ptrace.h to appropriate place. 2015-11-24 14:24:46 +02:00
interception libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
libbacktrace
lsan libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
sanitizer_common libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
tsan re PR sanitizer/68824 (libtsan is missing the __interceptor___tls_get_addr symbol without bumping the soname) 2016-01-19 13:45:54 +01:00
ubsan
acinclude.m4
aclocal.m4
ChangeLog re PR sanitizer/71160 (libasan: Backport support for malloc within dlsym) 2016-05-17 11:17:54 +02:00
config.h.in
configure configure.ac: Replace the hard-coded -ldl requirement for link_sanitizer_common with a... 2016-01-14 21:27:49 +01:00
configure.ac configure.ac: Replace the hard-coded -ldl requirement for link_sanitizer_common with a... 2016-01-14 21:27:49 +01:00
configure.tgt libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
HOWTO_MERGE
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in
MERGE libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +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.