gcc/libsanitizer
David S. Miller c84733360b Fix sanitizer build on sparc.
* sanitizer_common/sanitizer_platform_limits_linux.cc (time_t):
	Define at __kernel_time_t, as needed for sparc.
	(struct __old_kernel_stat): Don't check if __sparc__ is defined.
	* libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
	(__sanitizer): Define struct___old_kernel_stat_sz,
	struct_kernel_stat_sz, and struct_kernel_stat64_sz for sparc.
	(__sanitizer_ipc_perm): Adjust for sparc targets.
	(__sanitizer_shmid_ds): Likewsie.
	(__sanitizer_sigaction): Likewsie.
	(IOC_SIZE): Likewsie.

From-SVN: r216224
2014-10-14 14:20:46 -07:00
..
asan [libsanitizer merge from upstream r218156] 2014-09-23 17:59:53 +00:00
include [libsanitizer merge from upstream r218156] 2014-09-23 17:59:53 +00:00
interception [libsanitizer merge from upstream r218156] 2014-09-23 17:59:53 +00:00
libbacktrace
lsan [libsanitizer merge from upstream r218156] 2014-09-23 17:59:53 +00:00
sanitizer_common Fix sanitizer build on sparc. 2014-10-14 14:20:46 -07:00
tsan [libsanitizer merge from upstream r218156] 2014-09-23 17:59:53 +00:00
ubsan Makefile.am (DEFS): Add -DPIC. 2014-10-14 17:56:52 +02:00
ChangeLog Fix sanitizer build on sparc. 2014-10-14 14:20:46 -07:00
LICENSE.TXT
MERGE [libsanitizer merge from upstream r218156] 2014-09-23 17:59:53 +00:00
Makefile.am
Makefile.in
README.gcc
acinclude.m4
aclocal.m4
config.h.in
configure
configure.ac
configure.tgt [AArch64] Enable Address Sanitizer. 2014-09-26 15:07:42 +02: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.