summaryrefslogtreecommitdiff
path: root/libsanitizer
diff options
context:
space:
mode:
authorkcc <kcc@138bc75d-0d04-0410-961f-82ee72b054a4>2012-11-21 15:07:31 +0000
committerkcc <kcc@138bc75d-0d04-0410-961f-82ee72b054a4>2012-11-21 15:07:31 +0000
commitc8b20ad802c72847310fe03758bb49ede3de6e22 (patch)
tree444de0ed199f14e19d99c93c2ce61bbe968f2b86 /libsanitizer
parent8dd7dbd1a1bd40f89d7ce5d2e3209e2145b6abdc (diff)
downloadgcc-c8b20ad802c72847310fe03758bb49ede3de6e22.tar.gz
extend libsanitizer/README.gcc
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@193698 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libsanitizer')
-rw-r--r--libsanitizer/ChangeLog4
-rw-r--r--libsanitizer/README.gcc19
2 files changed, 19 insertions, 4 deletions
diff --git a/libsanitizer/ChangeLog b/libsanitizer/ChangeLog
index 22f65b29926..488a1539914 100644
--- a/libsanitizer/ChangeLog
+++ b/libsanitizer/ChangeLog
@@ -1,3 +1,7 @@
+2012-11-21 Kostya Serebryany <kcc@google.com>
+
+ * README.gcc: Extend the README.gcc with mode details.
+
2012-11-20 Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
* sanitizer_common/sanitizer_linux.cc
diff --git a/libsanitizer/README.gcc b/libsanitizer/README.gcc
index 0f807036052..8fb0a932b40 100644
--- a/libsanitizer/README.gcc
+++ b/libsanitizer/README.gcc
@@ -1,4 +1,15 @@
-The AddressSanitizer (http://code.google.com/p/address-sanitizer) is
-a project developed by Google Inc. The source files of the project
-are hosted at http://llvm.org/svn/llvm-project/compiler-rt. These files
-are the ones in the asan subdirectory of that project.
+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.