public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111693] -Wuse-after-free is documented in the wrong location
Date: Wed, 04 Oct 2023 20:10:58 +0000 [thread overview]
Message-ID: <bug-111693-4-uuA3UW59Yg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111693-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111693
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> The easiest way to find documentation for an option is to look at the index
> located at:
> https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Option-Index.html
>
> And search for the option.
You should also be able to find it in the option summary:
https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Option-Summary.html
But it's not there.
next prev parent reply other threads:[~2023-10-04 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:01 [Bug c/111693] New: Online manual mentions -Wuse-after-free but does not document it further jonathan.leffler at gmail dot com
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 [this message]
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-uuA3UW59Yg@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).