mirrors/gcc
0
0
Fork 0
mirror of https://gcc.gnu.org/git/gcc.git synced 2024-11-30 15:24:07 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
cd0be65c26
gcc/libsanitizer
History
Wei Mi cd0be65c26 tsan: New directory. 
libsanitizer/
	* tsan: New directory. Import tsan runtime from llvm.
	* configure.ac: Add 64 bits tsan build.
	* Makefile.am: Likewise.
	* configure: Regenerated.
	* Makefile.in: Likewise.

From-SVN: r193737
2012-11-22 22:03:11 +00:00
..
asan configure.ac: Invoke AM_MAINTAINER_MODE. 2012-11-16 15:19:15 +00:00
include/sanitizer Define/use hardware pointer type for stack unwind 2012-11-16 04:02:29 -08:00
interception configure.ac: Invoke AM_MAINTAINER_MODE. 2012-11-16 15:19:15 +00:00
sanitizer_common Fix sanitizer build on sparc64. 2012-11-20 12:54:49 -08:00
tsan tsan: New directory. 2012-11-22 22:03:11 +00:00
acinclude.m4 Update configure.ac for GCC tree and remove unused files 2012-11-13 16:02:12 -08:00
aclocal.m4 configure.ac: Invoke AM_MAINTAINER_MODE. 2012-11-16 15:19:15 +00:00
ChangeLog tsan: New directory. 2012-11-22 22:03:11 +00:00
configure tsan: New directory. 2012-11-22 22:03:11 +00:00
configure.ac tsan: New directory. 2012-11-22 22:03:11 +00:00
configure.tgt Enable building of libsanitizer on sparc linux 2012-11-16 09:11:03 +01:00
libtool-version
LICENSE.TXT
Makefile.am tsan: New directory. 2012-11-22 22:03:11 +00:00
Makefile.in tsan: New directory. 2012-11-22 22:03:11 +00:00
README.gcc extend libsanitizer/README.gcc 2012-11-21 15:07:31 +00: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

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.