From: Tobias Burnus <burnus@net-b.de>
To: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
Cc: gcc patches <gcc-patches@gcc.gnu.org>,
Dodji Seketeli <dodji@redhat.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [wwwdocs] Mention -faddress-sanitizer in gcc-4.8/changes.html
Date: Fri, 23 Nov 2012 11:28:00 -0000 [thread overview]
Message-ID: <50AF5DA3.9040803@net-b.de> (raw)
In-Reply-To: <CAGQ9bdzTE=mzwQdzAOmi=Ju3NFOVs9KOvzVNU0xHusq5JDUnVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Konstantin Serebryany wrote:
> On Mon, Nov 19, 2012 at 10:44 PM, Tobias Burnus <burnus@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
[-- Attachment #2: changes.diff --]
[-- Type: text/x-patch, Size: 1228 bytes --]
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>
next prev parent reply other threads:[~2012-11-23 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 18:45 Tobias Burnus
2012-11-20 5:06 ` Konstantin Serebryany
2012-11-23 11:28 ` Tobias Burnus [this message]
2012-11-23 12:21 ` Konstantin Serebryany
2012-11-23 13:22 ` Tobias Burnus
2012-11-23 13:25 ` Konstantin Serebryany
2012-11-23 13:30 ` Tobias Burnus
2012-11-23 13:34 ` Konstantin Serebryany
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50AF5DA3.9040803@net-b.de \
--to=burnus@net-b.de \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=konstantin.s.serebryany@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).