gcc/libsanitizer
Martin Liska b3d566f570
Update merge.sh to reflect usage of git.
After switching to GIT, we should use it in libsanitizer
merge script. I'll do merge from master as soon as
PR95311 gets fixed.

I'm going to install the patch.

libsanitizer/ChangeLog:

	* LOCAL_PATCHES: Use git hash instead of SVN id.
	* merge.sh: Use git instead of VCS.  Update paths
	relative to upstream git repository.
2020-05-26 08:48:14 +02:00
..
asan
builtins
include
interception
libbacktrace
lsan
sanitizer_common libsanitizer: Add missing file and regen Makefile.in 2020-05-01 16:24:37 +02:00
tsan
ubsan
acinclude.m4
aclocal.m4
ChangeLog x86: Also check if -fcf-protection works 2020-05-15 09:07:17 -07:00
config.h.in
configure x86: Also check if -fcf-protection works 2020-05-15 09:07:17 -07:00
configure.ac
configure.tgt gcc: Enable bits for sanitizer support on FreeBSD x86_64 2020-05-01 17:18:47 +02:00
HOWTO_MERGE
libsanitizer.spec.in
LICENSE.TXT
LOCAL_PATCHES Update merge.sh to reflect usage of git. 2020-05-26 08:48:14 +02:00
Makefile.am
Makefile.in
MERGE
merge.sh Update merge.sh to reflect usage of git. 2020-05-26 08:48:14 +02: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.