gcc/libsanitizer
Yury Gribov 2621c86043 re PR sanitizer/59106 (Failure to link against static libasan)
libsanitizer:
2013-11-18  Yury Gribov  <y.gribov@samsung.com>

	PR sanitizer/59106
	* asan/Makefile.am (AM_CXXFLAGS): Add -fno-rtti.
	* interception/Makefile.am (AM_CXXFLAGS): Likewise.
	* lsan/Makefile.am (AM_CXXFLAGS): Likewise.
	* sanitizer_common/Makefile.am (AM_CXXFLAGS): Likewise.
	* tsan/Makefile.am (AM_CXXFLAGS): Likewise.
	* asan/Makefile.in: Regenerate.
	* interception/Makefile.in: Regenerate.
	* tsan/Makefile.in: Regenerate.
	* lsan/Makefile.in: Regenerate.
	* sanitizer_common/Makefile.in: Regenerate.

gcc/testsuite:
2013-11-18  Yury Gribov  <y.gribov@samsung.com>

	PR sanitizer/59106
	* c-c++-common/asan/pr59106.c: New test.

From-SVN: r204934
2013-11-18 08:03:16 +00:00
..
asan re PR sanitizer/59106 (Failure to link against static libasan) 2013-11-18 08:03:16 +00:00
include/sanitizer
interception re PR sanitizer/59106 (Failure to link against static libasan) 2013-11-18 08:03:16 +00:00
lsan re PR sanitizer/59106 (Failure to link against static libasan) 2013-11-18 08:03:16 +00:00
sanitizer_common re PR sanitizer/59106 (Failure to link against static libasan) 2013-11-18 08:03:16 +00:00
tsan re PR sanitizer/59106 (Failure to link against static libasan) 2013-11-18 08:03:16 +00:00
ubsan
acinclude.m4
aclocal.m4
ChangeLog re PR sanitizer/59106 (Failure to link against static libasan) 2013-11-18 08:03:16 +00:00
configure
configure.ac
configure.tgt
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in
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

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.