gcc/libsanitizer
Jakub Jelinek 4abc46b51a re PR sanitizer/92154 (new glibc breaks arm bootstrap due to libsanitizer)
PR sanitizer/92154
	* sanitizer_common/sanitizer_platform_limits_posix.h: Cherry-pick
	llvm-project revision 947f9692440836dcb8d88b74b69dd379d85974ce.
	* sanitizer_common/sanitizer_platform_limits_posix.cpp: Likewise.

From-SVN: r278722
2019-11-26 10:08:31 +01:00
..
asan Reapply all revisions mentioned in LOCAL_PATCHES. 2019-11-07 09:34:14 +00:00
builtins
include Libsanitizer: merge from trunk 2019-11-07 09:33:54 +00:00
interception Libsanitizer: merge from trunk with merge.sh. 2019-11-05 13:54:57 +00:00
libbacktrace
lsan Update comment in libsanitizer/*/libtool-version files. 2019-11-20 14:52:05 +00:00
sanitizer_common re PR sanitizer/92154 (new glibc breaks arm bootstrap due to libsanitizer) 2019-11-26 10:08:31 +01:00
tsan Update comment in libsanitizer/*/libtool-version files. 2019-11-20 14:52:05 +00:00
ubsan Update comment in libsanitizer/*/libtool-version files. 2019-11-20 14:52:05 +00:00
acinclude.m4
aclocal.m4
ChangeLog re PR sanitizer/92154 (new glibc breaks arm bootstrap due to libsanitizer) 2019-11-26 10:08:31 +01:00
config.h.in
configure
configure.ac
configure.tgt Enable libsanitizer build on riscv64 2019-11-13 09:45:15 +00:00
HOWTO_MERGE
libsanitizer.spec.in
LICENSE.TXT
LOCAL_PATCHES Update LOCAL_PATCHES. 2019-11-07 09:34:42 +00:00
Makefile.am
Makefile.in
MERGE Libsanitizer: merge from trunk 2019-11-07 09:33:54 +00:00
merge.sh Libsanitizer: merge from trunk 2019-11-07 09:33:54 +00:00
README.gcc

AddressSanitizer and ThreadSanitizer (https://github.com/google/sanitizers) 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
https://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.