From d67f6589bf710235ad56731c4c06a75cfad75462 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Fri, 14 Dec 2012 11:32:23 +0100
Subject: open_issues/gcc: a1d48e100791bc67ff355e0931a604e767c827b7
 (2012-12-10; be3860ba8df48cca3253da4f02fd2d42d856ce80 (2012-12-10))

---
 open_issues/code_analysis.mdwn | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

(limited to 'open_issues/code_analysis.mdwn')

diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index b3908243..8c604e3f 100644
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -137,11 +137,20 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
         <youpi> ah, no, the libthreads code properly sets the guard, just for
           grow-up stacks
 
-  * GCC's AddressSanitizer (ASan; `-faddress-sanitizer`)
+  * GCC's AddressSanitizer, a memory error detector (ASan;
+    `-fsanitize=address`)
 
     [Finding races and memory errors with GCC instrumentation
     (AddressSanitizer)](http://gcc.gnu.org/wiki/cauldron2012#Finding_races_and_memory_errors_with_GCC_instrumentation_.28AddressSanitizer.29),
-    GNU Tools Cauldron 2012.
+    GNU Tools Cauldron 2012.  <http://code.google.com/p/address-sanitizer/>.
+
+    Not yet [[ported to the Hurd|community/gsoc/project_ideas/gcc_asan]].
+
+  * GCC's ThreadSanitizer, a data race detector (TSan; `-fsanitize=thread`)
+
+    <http://code.google.com/p/data-race-test/wiki/ThreadSanitizer>
+
+    Not yet [[ported to the Hurd|community/gsoc/project_ideas/gcc_asan]].
 
   * Input fuzzing
 
-- 
cgit v1.2.3