gcc/libsanitizer
Iain Sandoe 639f51ba26 libsanitizer, record a local patch.
2019-08-16  Iain Sandoe  <iain@sandoe.co.uk>

	* LOCAL_PATCHES: Add r274585.

From-SVN: r274586
2019-08-16 19:49:07 +00:00
..
asan libsanitize, asan - reapply r272406 2019-08-16 19:46:09 +00:00
builtins Libsanitizer merge from trunk r368656. 2019-08-14 08:47:11 +00:00
include Libsanitizer merge from trunk r368656. 2019-08-14 08:47:11 +00:00
interception [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
libbacktrace [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
lsan [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
sanitizer_common [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
tsan Reapply missing patch for libsanitizer. 2019-08-15 15:31:46 +00:00
ubsan [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
acinclude.m4
aclocal.m4 [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
ChangeLog libsanitizer, record a local patch. 2019-08-16 19:49:07 +00:00
config.h.in
configure [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
configure.ac
configure.tgt Libsanitizer merge from trunk r368656. 2019-08-14 08:47:11 +00:00
HOWTO_MERGE
libsanitizer.spec.in
libtool-version
LICENSE.TXT
LOCAL_PATCHES libsanitizer, record a local patch. 2019-08-16 19:49:07 +00:00
Makefile.am
Makefile.in [libsanitizer] Fix PR bootstrap/91455 2019-08-15 14:13:10 +00:00
MERGE Libsanitizer merge from trunk r368656. 2019-08-14 08:47:11 +00:00
merge.sh Libsanitizer merge from trunk r368656. 2019-08-14 08:47:11 +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.