diff options
| author | Kostya Serebryany <kcc@google.com> | 2012-11-21 15:07:31 +0000 |
|---|---|---|
| committer | Kostya Serebryany <kcc@gcc.gnu.org> | 2012-11-21 15:07:31 +0000 |
| commit | 5cba83a8a70c9431dc5fc83e93ca09e615cdff02 (patch) | |
| tree | 444de0ed199f14e19d99c93c2ce61bbe968f2b86 | |
| parent | aaaefb9d5a04e28ec89e8fc564076d8eae18ca93 (diff) | |
| download | gcc-5cba83a8a70c9431dc5fc83e93ca09e615cdff02.zip gcc-5cba83a8a70c9431dc5fc83e93ca09e615cdff02.tar.gz gcc-5cba83a8a70c9431dc5fc83e93ca09e615cdff02.tar.bz2 | |
extend libsanitizer/README.gcc
From-SVN: r193698
| -rw-r--r-- | libsanitizer/ChangeLog | 4 | ||||
| -rw-r--r-- | libsanitizer/README.gcc | 19 |
2 files changed, 19 insertions, 4 deletions
diff --git a/libsanitizer/ChangeLog b/libsanitizer/ChangeLog index 22f65b2..488a153 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 0f80703..8fb0a93 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. |