public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug sanitizer/59353] New: -fsanitize=return is not documented
@ 2013-11-30 13:32 burnus at gcc dot gnu.org
  2013-11-30 13:35 ` [Bug sanitizer/59353] " burnus at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-11-30 13:32 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59353

            Bug ID: 59353
           Summary: -fsanitize=return is not documented
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                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,
                    mpolacek at gcc dot gnu.org

Seems as if -fsanitize=return is now supported, but now yet documented in
invoke.texi


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug sanitizer/59353] -fsanitize=return is not documented
  2013-11-30 13:32 [Bug sanitizer/59353] New: -fsanitize=return is not documented burnus at gcc dot gnu.org
@ 2013-11-30 13:35 ` burnus at gcc dot gnu.org
  2013-11-30 13:44 ` mpolacek at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-11-30 13:35 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59353

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
And looking at
https://code.google.com/p/address-sanitizer/wiki/ExampleUseAfterReturn - it
seems as if the options is called -fsanitize=use-after-return with Clang.
Having different names for the same feature is a bit unfortunate, too.
Especially as GCC -fsanitize= links to Wiki pages which are Clang centric.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug sanitizer/59353] -fsanitize=return is not documented
  2013-11-30 13:32 [Bug sanitizer/59353] New: -fsanitize=return is not documented burnus at gcc dot gnu.org
  2013-11-30 13:35 ` [Bug sanitizer/59353] " burnus at gcc dot gnu.org
@ 2013-11-30 13:44 ` mpolacek at gcc dot gnu.org
  2013-12-02 20:39 ` mpolacek at gcc dot gnu.org
  2013-12-02 20:40 ` mpolacek at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2013-11-30 13:44 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59353

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2013-11-30
           Assignee|unassigned at gcc dot gnu.org      |mpolacek at gcc dot gnu.org
   Target Milestone|---                         |4.9.0
     Ever confirmed|0                           |1

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
As for the doc, I'll do it.

But note that -fsanitize=return and -fsanitize=use-after-return are two
different options: -fsanitize=return is a part of ubsan and checks that the
function doesn't have a missing "return" statement (currently done only for
C++).
-fsanitize=use-after-return is described in the link you provided and is a part
of asan.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug sanitizer/59353] -fsanitize=return is not documented
  2013-11-30 13:32 [Bug sanitizer/59353] New: -fsanitize=return is not documented burnus at gcc dot gnu.org
  2013-11-30 13:35 ` [Bug sanitizer/59353] " burnus at gcc dot gnu.org
  2013-11-30 13:44 ` mpolacek at gcc dot gnu.org
@ 2013-12-02 20:39 ` mpolacek at gcc dot gnu.org
  2013-12-02 20:40 ` mpolacek at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2013-12-02 20:39 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59353

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Mon Dec  2 20:39:25 2013
New Revision: 205601

URL: http://gcc.gnu.org/viewcvs?rev=205601&root=gcc&view=rev
Log:
    PR sanitizer/59353
    * doc/invoke.texi: Document -fsanitize=return.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/doc/invoke.texi


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug sanitizer/59353] -fsanitize=return is not documented
  2013-11-30 13:32 [Bug sanitizer/59353] New: -fsanitize=return is not documented burnus at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  2013-12-02 20:39 ` mpolacek at gcc dot gnu.org
@ 2013-12-02 20:40 ` mpolacek at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2013-12-02 20:40 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59353

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-12-02 20:40 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-30 13:32 [Bug sanitizer/59353] New: -fsanitize=return is not documented burnus at gcc dot gnu.org
2013-11-30 13:35 ` [Bug sanitizer/59353] " burnus at gcc dot gnu.org
2013-11-30 13:44 ` mpolacek at gcc dot gnu.org
2013-12-02 20:39 ` mpolacek at gcc dot gnu.org
2013-12-02 20:40 ` mpolacek at gcc dot gnu.org

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).