gcc/libsanitizer
Jakub Jelinek 81c87471e9 re PR sanitizer/60055 (Invalid binding of __tsan_default_options)
PR sanitizer/60055
	* tsan/tsan_flags.cc (__tsan_default_options): Add
	SANITIZER_INTERFACE_ATTRIBUTE.  Backport from upstream r200747.
	* tsan/tsan_rtl.cc (__tsan::OnFinalize): Likewise.

From-SVN: r207459
2014-02-04 11:46:22 +01:00
..
asan
include
interception
libbacktrace * sanitizer_common/sanitizer_symbolizer_libbacktrace.h 2014-01-09 19:16:40 +01:00
lsan
sanitizer_common re PR sanitizer/60038 (AddressSanitizer CHECK failed ... "((*tls_addr + *tls_size)) <= ((*stk_addr + *stk_size))" on CentOS 5.10) 2014-02-04 08:37:44 +01:00
tsan re PR sanitizer/60055 (Invalid binding of __tsan_default_options) 2014-02-04 11:46:22 +01:00
ubsan
acinclude.m4
aclocal.m4
ChangeLog re PR sanitizer/60055 (Invalid binding of __tsan_default_options) 2014-02-04 11:46:22 +01:00
config.h.in * sanitizer_common/sanitizer_symbolizer_libbacktrace.h 2014-01-09 19:16:40 +01:00
configure re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
configure.ac re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
configure.tgt
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +00:00
Makefile.in re PR sanitizer/57316 (build failure in libsanitizer) 2014-01-23 14:32:05 +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.