public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/71283] Inconsistent location for C++ warning options in the manual
Date: Fri, 04 Mar 2022 17:56:50 +0000 [thread overview]
Message-ID: <bug-71283-4-6VZoIkhxwu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-71283-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283
Barry Revzin <barry.revzin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #17 from Barry Revzin <barry.revzin at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> That is because this is C++ only option. It is listed under
> https://gcc.gnu.org/onlinedocs/gcc-6.1.0/gcc/C_002b_002b-Dialect-Options.
> html#C_002b_002b-Dialect-Options :
>
> -Wno-terminate (C++ and Objective-C++ only)
> Disable the warning about a throw-expression that will immediately result in
> a call to terminate.
>
> This is exact location for all other C++ only options are located.
>
> So not a bug.
Sure, but right now some warnings are under Warning Options and others are
under Dialect Options. I would never think to look for warnings under dialect
options, since my initial thought would be that the latter is for the kinds of
things that show up first on that page... -fabi-version, -fchar8_t, etc. You
have to go pretty far down that page to get to warnings. -Wsuggest-override
used to be under Warning Options, was recently moved to Dialect Options for
instance.
I would like to request that either all the warning options are documented
under warning options, or that there is one page for all the C++ warning
options (as distinct from "dialect options"), or something else along those
lines. The current split is a bit confusing and makes it hard to find warnings.
next prev parent reply other threads:[~2022-03-04 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-71283-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` jakub at gcc dot gnu.org
2021-06-01 8:08 ` rguenth at gcc dot gnu.org
2021-06-01 12:03 ` redi at gcc dot gnu.org
2021-07-01 8:07 ` egallager at gcc dot gnu.org
2021-07-01 8:15 ` marxin at gcc dot gnu.org
2022-03-04 17:56 ` barry.revzin at gmail dot com [this message]
2023-10-10 20:29 ` egallager 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-71283-4-6VZoIkhxwu@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).