OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
05abad4cca
gcc/libsanitizer
History
Martin Liska 05abad4cca invoke.texi: Document the options. 
gcc/
	* doc/invoke.texi: Document the options.
	* flag-types.h (enum sanitize_code): Add
	SANITIZE_POINTER_COMPARE and SANITIZE_POINTER_SUBTRACT.
	* ipa-inline.c (sanitize_attrs_match_for_inline_p): Add handling
	of SANITIZE_POINTER_COMPARE and SANITIZE_POINTER_SUBTRACT.
	* opts.c: Define new sanitizer options.
	* sanitizer.def (BUILT_IN_ASAN_POINTER_COMPARE): Likewise.
	(BUILT_IN_ASAN_POINTER_SUBTRACT): Likewise.
gcc/c/
	* c-typeck.c (pointer_diff): Add new argument and instrument
	pointer subtraction.
	(build_binary_op): Similar for pointer comparison.
gcc/cp/
	* typeck.c (pointer_diff): Add new argument and instrument
	pointer subtraction.
	(cp_build_binary_op): Create compound expression if doing an
	instrumentation.
gcc/testsuite/
	* c-c++-common/asan/pointer-compare-1.c: New test.
	* c-c++-common/asan/pointer-compare-2.c: New test.
	* c-c++-common/asan/pointer-subtract-1.c: New test.
	* c-c++-common/asan/pointer-subtract-2.c: New test.
	* c-c++-common/asan/pointer-subtract-3.c: New test.
	* c-c++-common/asan/pointer-subtract-4.c: New test.
libsanitizer/
	* asan/asan_descriptions.cc: Cherry-pick upstream r319668.
	* asan/asan_descriptions.h: Likewise.
	* asan/asan_report.cc: Likewise.
	* asan/asan_thread.cc: Likewise.
	* asan/asan_thread.h: Likewise.

Co-Authored-By: Jakub Jelinek <jakub@redhat.com>

From-SVN: r255404
2017-12-05 10:23:25 +01:00
..
asan invoke.texi: Document the options. 2017-12-05 10:23:25 +01:00
builtins ubsan.c (ubsan_expand_null_ifn): Use _v1 suffixed type mismatch builtins... 2017-10-19 13:23:59 +02:00
include ubsan.c (ubsan_expand_null_ifn): Use _v1 suffixed type mismatch builtins... 2017-10-19 13:23:59 +02:00
interception Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
libbacktrace Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
lsan Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
sanitizer_common Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
tsan Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
ubsan Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
acinclude.m4 Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
aclocal.m4
ChangeLog invoke.texi: Document the options. 2017-12-05 10:23:25 +01:00
config.h.in
configure Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
configure.ac Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
configure.tgt Add sanitizer_linux_x86_64.lo if __x86_64__ is defined by $CC 2017-10-05 03:39:32 -07:00
HOWTO_MERGE re PR sanitizer/78307 (missing symbols in libubsan without changing the soname) 2016-11-16 13:13:19 +02:00
libsanitizer.spec.in
libtool-version
LICENSE.TXT
LOCAL_PATCHES Add PR sanitizer/78532 patch to libsanitizer/LOCAL_PATCHES. 2016-11-30 14:32:55 +02:00
Makefile.am ubsan.c (ubsan_expand_null_ifn): Use _v1 suffixed type mismatch builtins... 2017-10-19 13:23:59 +02:00
Makefile.in Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
MERGE ubsan.c (ubsan_expand_null_ifn): Use _v1 suffixed type mismatch builtins... 2017-10-19 13:23:59 +02:00
merge.sh re PR sanitizer/79168 (libtsan fails to link when cross compiling GCC tip for Aarch64 target) 2017-01-24 01:18:36 +01:00
README.gcc

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.