public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "smagnet at yopmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/67204] New: documentation for sanitizer missing/incomplete Date: Thu, 13 Aug 2015 10:21:00 -0000 [thread overview] Message-ID: <bug-67204-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67204 Bug ID: 67204 Summary: documentation for sanitizer missing/incomplete Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: smagnet at yopmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target Milestone: --- The GCC manual contains next to no documentation about the use of the various -fsanitize options. At the moment, the best source of information are 3rd party sites like the google AddressSanitizer wiki <https://code.google.com/p/address-sanitizer/wiki/AddressSanitizer> which refer primarily to LLVM/Clang; it's not clear how applicable they are to the current sanitizer implementations in GCC. The GCC manual should contain a proper description of the sanitizer functionality.
next reply other threads:[~2015-08-13 10:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-13 10:21 smagnet at yopmail dot com [this message] 2015-08-13 10:26 ` [Bug sanitizer/67204] " mpolacek at gcc dot gnu.org 2015-08-13 10:29 ` pinskia at gcc dot gnu.org 2015-08-13 10:46 ` smagnet at yopmail dot com 2015-08-13 11:01 ` trippels at gcc dot gnu.org 2015-08-13 11:16 ` mpolacek at gcc dot gnu.org 2015-08-17 9:04 ` y.gribov at samsung dot com 2015-08-17 10:07 ` manu at gcc dot gnu.org 2015-08-17 12:15 ` dvyukov at google dot com 2015-08-17 12:51 ` mpolacek at gcc dot gnu.org
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=bug-67204-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).