OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gcc/libsanitizer
History
Igor Tsimbalist 9069eb28d4 Enable building libsanitizer with Intel CET 
libsanitizer/
	* acinclude.m4: Add enable.m4 and cet.m4.
	* Makefile.in: Regenerate.
	* asan/Makefile.am: Update AM_CXXFLAGS.
	* asan/Makefile.in: Regenerate.
	* configure: Likewise.
	* configure.ac: Set CET_FLAGS. Update EXTRA_CFLAGS,
	EXTRA_CXXFLAGS, EXTRA_ASFLAGS.
	* interception/Makefile.am: Update AM_CXXFLAGS.
	* interception/Makefile.in: Regenerate.
	* libbacktrace/Makefile.am: Update AM_CFLAGS, AM_CXXFLAGS.
	* libbacktrace/Makefile.in: Regenerate.
	* lsan/Makefile.am: Update AM_CXXFLAGS.
	* lsan/Makefile.in: Regenerate.
	* sanitizer_common/Makefile.am: Update AM_CXXFLAGS,
	AM_CCASFLAGS.
	* sanitizer_common/sanitizer_linux_x86_64.S: Include cet.h.
	Add _CET_ENDBR macro.
	* sanitizer_common/Makefile.in: Regenerate.
	* tsan/Makefile.am: Update AM_CXXFLAGS.
	* tsan/Makefile.in: Regenerate.
	* tsan/tsan_rtl_amd64.S Include cet.h. Add _CET_ENDBR macro.
	* ubsan/Makefile.am: Update AM_CXXFLAGS.
	* ubsan/Makefile.in: Regenerate.

From-SVN: r254896
 		2017-11-17 22:34:50 +01:00
..
asan Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +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
ChangeLog Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
HOWTO_MERGE re PR sanitizer/78307 (missing symbols in libubsan without changing the soname) 2016-11-16 13:13:19 +02:00
LICENSE.TXT
…
LOCAL_PATCHES Add PR sanitizer/78532 patch to libsanitizer/LOCAL_PATCHES. 2016-11-30 14:32:55 +02:00
MERGE ubsan.c (ubsan_expand_null_ifn): Use _v1 suffixed type mismatch builtins... 2017-10-19 13:23:59 +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
README.gcc re PR sanitizer/59136 (llvm-symbolizer shouldn't be started always) 2014-01-09 19:13:39 +01:00
acinclude.m4 Enable building libsanitizer with Intel CET 2017-11-17 22:34:50 +01:00
aclocal.m4 libsanitizer: Bump to automake 1.11.6 2015-05-13 11:11:58 +00:00
config.h.in re PR sanitizer/64839 (libsanitizer shouldn't require <rpc/xdr.h>) 2015-04-13 08:59:55 +00:00
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
libsanitizer.spec.in re PR sanitizer/59063 (ASAN: segfault in __interceptor_clock_gettime) 2013-11-29 12:30:36 +00:00
libtool-version
…
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 

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.