gcc/libsanitizer
Jakub Jelinek 0ce483917f re PR sanitizer/77396 (address sanitizer crashes if all static global variables are optimized)
PR sanitizer/77396
	* asan/asan_globals.cc: Cherry-pick upstream r280657.

	* g++.dg/asan/pr77396-2.C: New test.

From-SVN: r239998
2016-09-05 21:43:57 +02:00
..
asan re PR sanitizer/77396 (address sanitizer crashes if all static global variables are optimized) 2016-09-05 21:43:57 +02:00
include
interception Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
libbacktrace Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
lsan Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
sanitizer_common Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
tsan re PR sanitizer/71042 (libtsan requires __pointer_chk_guard@GLIBC_PRIVATE (6)) 2016-08-12 10:53:07 +02:00
ubsan Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
ChangeLog re PR sanitizer/77396 (address sanitizer crashes if all static global variables are optimized) 2016-09-05 21:43:57 +02:00
HOWTO_MERGE
LICENSE.TXT
MERGE
Makefile.am
Makefile.in Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
README.gcc
acinclude.m4
aclocal.m4
config.h.in
configure Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
configure.ac Revert 2015-11-09 sanitizer/obstack configury 2016-07-25 10:43:36 +09:30
configure.tgt
libsanitizer.spec.in
libtool-version
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.