gcc/libsanitizer
2013-10-23 21:30:54 +00:00
..
asan re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
include/sanitizer libsanitizer merge from upstream r175733 2013-02-21 10:57:10 +00:00
interception re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
sanitizer_common Merge ubsan into trunk. 2013-08-30 16:12:58 +00:00
tsan re PR other/43620 ([4.3 Release Blocker] Uploading to gnu.org will fail due to automake security issue) 2013-03-22 15:14:42 +01:00
ubsan darwin.h (LINK_COMMAND_SPEC_A): Revise sanitizer specs to include sanitize(undefined). 2013-09-01 12:16:07 +00:00
acinclude.m4
aclocal.m4
ChangeLog Fix up ChangeLog entries (name, e-mail, formatting, otherwise). 2013-10-23 21:30:54 +00:00
configure libtool.m4 (_LT_ENABLE_LOCK <ld -m flags>): Remove non-canonical ppc host match. 2013-09-20 19:17:52 +09:30
configure.ac Merge ubsan into trunk. 2013-08-30 16:12:58 +00:00
configure.tgt arm.c (arm_asan_shadow_offset): New function. 2013-05-07 16:17:50 +02:00
libtool-version
LICENSE.TXT
Makefile.am Merge ubsan into trunk. 2013-08-30 16:12:58 +00:00
Makefile.in Merge ubsan into trunk. 2013-08-30 16:12:58 +00:00
MERGE libsanitizer merge from upstream r175733 2013-02-21 10:57:10 +00:00
merge.sh Merge ubsan into trunk. 2013-08-30 16:12:58 +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.
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.