Konstantin Serebryany wrote:
On Mon, Nov 19, 2012 at 10:44 PM, Tobias Burnus <bur...@net-b.de> wrote:
attached is a first draft for -faddress-sanitizer in the release notes.
stack overflow is something different, I guess we want to say "stack
buffer overflow". I typically write something like "heap-, stack-, and global-
buffer
overflow as well as use-after-free bugs".
Fixed. See attached updated patch.
I also suggest adding "use -O1 or higher for better performance"
because otherwise "fast memory error detector" is not really true.
Is that needed? I think that's obvious that -O0 is not that fast.
Notes: I didn't mention Sparc, PowerPC, and Darwin as those aren't yet
available. I kept the current wording for ASAN even though global and
stack overflow are to my knowledge not yet available.
Tobias
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.63
diff -u -p -r1.63 changes.html
--- changes.html 21 Nov 2012 10:19:27 -0000 1.63
+++ changes.html 23 Nov 2012 11:21:19 -0000
@@ -110,6 +110,18 @@ by this change.</p>
inlining decisions (for example in the case of Fortran
array descriptors) and devirtualization.</li>
</ul></li>
+ <li><a href="https://code.google.com/p/address-sanitizer/";>AddressSanitizer
+ </a>, a fast memory error detector, has been added and can be
+ enabled via <code>-fsanitize=address</code>. Memory access
+ instructions will be instrumented to detect heap-, stack-, and
+ global-buffer overflow as well as use-after-free bugs. To get
+ nicer stacktraces, use <code>-fno-omit-frame-pointer</code>. The
+ AddressSanitizer is available on IA-32/x86-64/x32 Linux.</li>
+ <li><a href="https://code.google.com/p/data-race-test/wiki/ThreadSanitizer";
+ >ThreadSanitizer</a> has been added and can be enabled via
+ <code>-fsanitize=thread</code>. Instructions will be instrumented to
+ detect data races. The ThreadSanitizer is available on x86-64
+ Linux.</li>
</ul>
