gcc/libsanitizer
Michael Haubenwallner f3915b4249 libsanitizer: Bump to automake 1.11.6
2015-05-13  Michael Haubenwallner  <michael.haubenwallner@ssi-schaefer.com>

	* Makefile.in: Regenerated with automake-1.11.6.
	* aclocal.m4: Likewise.
	* asan/Makefile.in: Likewise.
	* configure: Likewise.
	* interception/Makefile.in: Likewise.
	* libbacktrace/Makefile.in: Likewise.
	* lsan/Makefile.in: Likewise.
	* sanitizer_common/Makefile.in: Likewise.
	* tsan/Makefile.in: Likewise.
	* ubsan/Makefile.in: Likewise.

From-SVN: r223140
2015-05-13 11:11:58 +00:00
..
asan libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
include
interception libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
libbacktrace libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
lsan libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
sanitizer_common libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
tsan libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
ubsan libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
acinclude.m4
aclocal.m4 libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
ChangeLog libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
config.h.in
configure libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
configure.ac
configure.tgt
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
MERGE
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.