gcc/libsanitizer
Max Ostapenko 9211bbb278 Move ptrace.h to appropriate place.
libsanitizer/

	* include/system/linux/asm/ptrace.h: Move to ...
	* include/system/asm/ptrace.h: ... this.

From-SVN: r230804
2015-11-24 14:24:46 +02:00
..
asan libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
include Move ptrace.h to appropriate place. 2015-11-24 14:24:46 +02:00
interception libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
libbacktrace Update libsanitizer obstack interceptors 2015-11-09 14:53:25 +10:30
lsan libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
sanitizer_common libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
tsan libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
ubsan Update libsanitizer obstack interceptors 2015-11-09 14:53:25 +10:30
acinclude.m4
aclocal.m4
ChangeLog Move ptrace.h to appropriate place. 2015-11-24 14:24:46 +02:00
config.h.in
configure Update libsanitizer obstack interceptors 2015-11-09 14:53:25 +10:30
configure.ac Update libsanitizer obstack interceptors 2015-11-09 14:53:25 +10:30
configure.tgt libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
HOWTO_MERGE Update HOWTO_MERGE file for libsanitizer. 2015-10-23 11:50:30 +03:00
libsanitizer.spec.in
libtool-version
LICENSE.TXT
Makefile.am
Makefile.in Update libsanitizer obstack interceptors 2015-11-09 14:53:25 +10:30
MERGE libsanitizer merge from upstream r253555. 2015-11-23 11:07:18 +02:00
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.