gcc/libsanitizer
Rainer Orth 2d509539db Guard against undefined weak symbols before Mac OS X 10.9 (PR sanitizer/82825)
PR sanitizer/82825
	* sanitizer_common/sanitizer_internal_defs.h: Cherry-pick upstream
	r??????.

From-SVN: r256813
2018-01-17 19:31:43 +00:00
..
asan invoke.texi: Document the options. 2017-12-05 10:23:25 +01:00
builtins
include
interception Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
libbacktrace Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
lsan Allow for lack of VM_MEMORY_OS_ALLOC_ONCE on Mac OS X (PR sanitizer/82824) 2018-01-13 21:01:27 +00:00
sanitizer_common Guard against undefined weak symbols before Mac OS X 10.9 (PR sanitizer/82825) 2018-01-17 19:31:43 +00:00
tsan Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
ubsan Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
acinclude.m4 Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
aclocal.m4
ChangeLog Guard against undefined weak symbols before Mac OS X 10.9 (PR sanitizer/82825) 2018-01-17 19:31:43 +00:00
config.h.in
configure Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
configure.ac Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
configure.tgt
HOWTO_MERGE
libsanitizer.spec.in
libtool-version
LICENSE.TXT
LOCAL_PATCHES
Makefile.am
Makefile.in Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01: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.