gcc/libsanitizer
Jakub Jelinek 19006c45f5 Makefile.am (AM_CXXFLAGS): Remove -Wno-c99-extensions.
* sanitizer_common/Makefile.am (AM_CXXFLAGS): Remove
	-Wno-c99-extensions.
	* interception/Makefile.am (AM_CXXFLAGS): Likewise.
	* asan/Makefile.am (AM_CXXFLAGS): Likewise.
	* sanitizer_common/Makefile.in: Regenerated.
	* interception/Makefile.in: Regenerated.
	* asan/Makefile.in: Regenerated.

From-SVN: r195229
2013-01-16 08:34:49 +01:00
..
asan Makefile.am (AM_CXXFLAGS): Remove -Wno-c99-extensions. 2013-01-16 08:34:49 +01:00
include/sanitizer libsanitizer mege from upstream r171973 2013-01-10 12:44:08 +00:00
interception Makefile.am (AM_CXXFLAGS): Remove -Wno-c99-extensions. 2013-01-16 08:34:49 +01:00
sanitizer_common Makefile.am (AM_CXXFLAGS): Remove -Wno-c99-extensions. 2013-01-16 08:34:49 +01:00
tsan re PR sanitizer/55488 (Implement cold calls in tsan run-time) 2013-01-10 17:57:34 +00:00
acinclude.m4
aclocal.m4 Add libstdc++-raw-cxx.m4 and use it in libsanitizer 2012-12-11 13:32:11 -08:00
ChangeLog Makefile.am (AM_CXXFLAGS): Remove -Wno-c99-extensions. 2013-01-16 08:34:49 +01:00
configure Remove "-I" from LIBSTDCXX_RAW_CXX_LDFLAGS 2013-01-07 10:23:42 -08:00
configure.ac Add libstdc++-raw-cxx.m4 and use it in libsanitizer 2012-12-11 13:32:11 -08:00
configure.tgt
libtool-version
LICENSE.TXT
Makefile.am Restore AM_MAKEFLAGS in libsanitizer 2012-12-12 07:41:36 -08:00
Makefile.in Restore AM_MAKEFLAGS in libsanitizer 2012-12-12 07:41:36 -08:00
MERGE libsanitizer mege from upstream r171973 2013-01-10 12:44:08 +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

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.