gcc/libsanitizer
Denis Khalikov 3b07c0e5e4 re PR sanitizer/86090 ([ASAN] ASAN does not properly configure libbacktrace.)
2018-06-13  Denis Khalikov  <d.khalikov@partner.samsung.com>

libsanitizer/

	PR sanitizer/86090
	* configure.ac: Check for lstat and readlink.
	* configure, config.h.in: Rebuild.

From-SVN: r261564
2018-06-13 22:51:42 +03:00
..
asan re PR sanitizer/85389 (posix_memalign() crash with address sanitizer when passing invalid arguments) 2018-04-18 09:02:40 +02:00
builtins
include
interception
libbacktrace
lsan
sanitizer_common re PR sanitizer/86012 (libsanitizer build failure on sparc64-linux-gnu) 2018-05-31 09:57:33 +00:00
tsan
ubsan
ChangeLog re PR sanitizer/86090 ([ASAN] ASAN does not properly configure libbacktrace.) 2018-06-13 22:51:42 +03:00
HOWTO_MERGE
LICENSE.TXT
LOCAL_PATCHES
MERGE
Makefile.am
Makefile.in
README.gcc
acinclude.m4
aclocal.m4
config.h.in re PR sanitizer/86090 ([ASAN] ASAN does not properly configure libbacktrace.) 2018-06-13 22:51:42 +03:00
configure re PR sanitizer/86090 ([ASAN] ASAN does not properly configure libbacktrace.) 2018-06-13 22:51:42 +03:00
configure.ac re PR sanitizer/86090 ([ASAN] ASAN does not properly configure libbacktrace.) 2018-06-13 22:51:42 +03:00
configure.tgt If someone has access to a 64-bit mips-linux system to test this (with the obvious edit), that'd be really nice. 2018-04-26 01:16:47 +00:00
libsanitizer.spec.in
libtool-version
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.