gcc/libsanitizer
Ian Lance Taylor 762c16eba6 libsanitizer: rename new libbacktrace symbols
* libbacktrace/backtrace-rename.h (backtrace_uncompress_lzma):
	Define.
	(backtrace_syminfo_to_full_callback): Define.
	(backtrace_syminfo_to_full_error_callback): Define.
2020-09-21 12:03:45 -07:00
..
asan libsanitizer: use gnu++14 2020-06-09 10:07:24 +02:00
builtins
include Libsanitizer: merge from master. 2020-06-02 08:02:07 +02:00
interception libsanitizer: use gnu++14 2020-06-09 10:07:24 +02:00
libbacktrace libsanitizer: rename new libbacktrace symbols 2020-09-21 12:03:45 -07:00
lsan libsanitizer: use gnu++14 2020-06-09 10:07:24 +02:00
sanitizer_common libsanitizer: Fix GetPcSpBp determination of SP on 32-bit Solaris/x86 2020-07-16 10:38:48 +02:00
tsan libsanitizer: use gnu++14 2020-06-09 10:07:24 +02:00
ubsan libsanitizer: use gnu++14 2020-06-09 10:07:24 +02:00
acinclude.m4
aclocal.m4
ChangeLog Daily bump. 2020-07-17 00:16:27 +00:00
config.h.in
configure Avoid nested save_CFLAGS and save_LDFLAGS 2020-05-29 12:56:40 -07:00
configure.ac
configure.tgt
HOWTO_MERGE Remove references to SVN in libsanitizer. 2020-05-29 11:50:54 +02:00
libsanitizer.spec.in
LICENSE.TXT
LOCAL_PATCHES Update link to LOCAL_PATCHES. 2020-06-02 08:03:48 +02:00
Makefile.am
Makefile.in
MERGE Libsanitizer: merge from master. 2020-06-02 08:02:07 +02:00
merge.sh Update merge.sh to reflect usage of git. 2020-05-26 08:48:14 +02:00
README.gcc Remove references to SVN in libsanitizer. 2020-05-29 11:50:54 +02:00

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://github.com/llvm/llvm-project in the following directories:
  compiler-rt/include/sanitizer
  compiler-rt/lib/sanitizer_common
  compiler-rt/lib/interception
  compiler-rt/lib/asan
  compiler-rt/lib/tsan
  compiler-rt/lib/lsan
  compiler-rt/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.