gcc/libsanitizer
Jakub Jelinek a745e44403 Fix up ChangeLog entry date.
From-SVN: r196965
2013-03-22 15:17:24 +01:00
..
asan re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
include/sanitizer libsanitizer merge from upstream r175733 2013-02-21 10:57:10 +00:00
interception re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
sanitizer_common re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
tsan re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
acinclude.m4
aclocal.m4
ChangeLog Fix up ChangeLog entry date. 2013-03-22 15:17:24 +01:00
configure Remove "-I" from LIBSTDCXX_RAW_CXX_LDFLAGS 2013-01-07 10:23:42 -08:00
configure.ac re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
configure.tgt configure.tgt: Disable build on darwin9 and earlier. 2013-02-11 23:13:37 +00:00
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
MERGE libsanitizer merge from upstream r175733 2013-02-21 10:57:10 +00:00
merge.sh Makefile.am (libasan_la_SOURCES): Remove deprecated dynamic/asan_interceptors_dynamic.cc. 2013-02-21 20:12:43 +01:00
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.