public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jonathan.leffler at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111693] New: Online manual mentions -Wuse-after-free but does not document it further
Date: Wed, 04 Oct 2023 17:01:56 +0000 [thread overview]
Message-ID: <bug-111693-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111693
Bug ID: 111693
Summary: Online manual mentions -Wuse-after-free but does not
document it further
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jonathan.leffler at gmail dot com
Target Milestone: ---
In the 13.2.0 documentation
(https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Warning-Options.html), the list
of options enabled by "-Wall" includes "-Wuse-after-free=2", but there is no
further mention of the option on the page.
Similarly, in the 12.3.0 documentation
(https://gcc.gnu.org/onlinedocs/gcc-12.3.0/gcc/Warning-Options.html), the list
of options enabled by "-Wall" includes "-Wuse-after-free=3", but there is no
further mention of the option on the page.
It is not mentioned at all in earlier manuals, presumably because it wasn't
available in the earlier versions.
It would be helpful to know what the values 2 and 3 mean, and presumably what 1
and 0 mean too.
next reply other threads:[~2023-10-04 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:01 jonathan.leffler at gmail dot com [this message]
2023-10-04 19:35 ` [Bug c/111693] " pinskia at gcc dot gnu.org
2023-10-04 19:37 ` pinskia at gcc dot gnu.org
2023-10-04 19:37 ` pinskia at gcc dot gnu.org
2023-10-04 19:58 ` jonathan.leffler at gmail dot com
2023-10-04 20:00 ` jonathan.leffler at gmail dot com
2023-10-04 20:02 ` jonathan.leffler at gmail dot com
2023-10-04 20:03 ` [Bug c/111693] -Wuse-after-free is documented in the wrong location pinskia at gcc dot gnu.org
2023-10-04 20:10 ` redi at gcc dot gnu.org
2023-10-04 20:12 ` egallager at gcc dot gnu.org
2024-01-17 4:52 ` cvs-commit at gcc dot gnu.org
2024-01-17 4:54 ` sandra at gcc dot gnu.org
2024-01-20 17:25 ` pinskia 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-111693-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: 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).