From cf38250e28f37bfdf2382473dd8fbd11b6f1e1ef Mon Sep 17 00:00:00 2001
From: Bill Wendling <isanbard@gmail.com>
Date: Sat, 29 Oct 2011 01:11:15 +0000
Subject: Revise ThreadSanitizer mention so that it lists the correct
 frontends.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@143268 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/ReleaseNotes.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'docs')

diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index 8adf813..c2d6283 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -558,9 +558,9 @@ object-oriented programming, operator overloading and strong typing.</p>
 <p><a href="http://code.google.com/p/data-race-test/">ThreadSanitizer</a> is a
    data race detector for (mostly) C and C++ code, available for Linux, Mac OS
    and Windows. On different systems, we use binary instrumentation frameworks
-   (Valgrind, Pin and DynamoRio) as frontends that generate the program events
-   for the race detection algorithm. On Linux, there's an option of using
-   LLVM-based compile-time instrumentation.</p>
+   (Valgrind and Pin) as frontends that generate the program events for the race
+   detection algorithm. On Linux, there's an option of using LLVM-based
+   compile-time instrumentation.</p>
 
 </div>
 
-- 
cgit v1.1