From 1bc5aee63eb72b341f506ad058502cd0361f0d10 Mon Sep 17 00:00:00 2001 From: Ben Cheng Date: Tue, 25 Mar 2014 22:37:19 -0700 Subject: Initial checkin of GCC 4.9.0 from trunk (r208799). Change-Id: I48a3c08bb98542aa215912a75f03c0890e497dba --- gcc-4.9/libsanitizer/README.gcc | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 gcc-4.9/libsanitizer/README.gcc (limited to 'gcc-4.9/libsanitizer/README.gcc') diff --git a/gcc-4.9/libsanitizer/README.gcc b/gcc-4.9/libsanitizer/README.gcc new file mode 100644 index 000000000..02698eb5c --- /dev/null +++ b/gcc-4.9/libsanitizer/README.gcc @@ -0,0 +1,20 @@ +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. -- cgit v1.2.3