From: David Malcolm <dmalcolm@redhat.com>
To: Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] c++: Add -Wexceptions warning option [PR97675]
Date: Thu, 05 Nov 2020 18:13:41 -0500 [thread overview]
Message-ID: <42878a70b164a5a67ac9f3456ec1adbe25e315e9.camel@redhat.com> (raw)
In-Reply-To: <20201105160318.107397-1-polacek@redhat.com>
On Thu, 2020-11-05 at 11:03 -0500, Marek Polacek via Gcc-patches wrote:
> This PR asks that we add a warning option for an existing (very old)
> warning, so that it can be disabled selectively. clang++ uses
> -Wexceptions for this, so I added this new option rather than using
> e.g. -Wnoexcept.
>
> gcc/c-family/ChangeLog:
>
> PR c++/97675
> * c.opt (Wexceptions): New option.
>
> gcc/cp/ChangeLog:
>
> PR c++/97675
> * except.c (check_handlers_1): Use OPT_Wexceptions for the
> warning. Use inform for the second part of the warning.
>
> gcc/ChangeLog:
>
> PR c++/97675
> * doc/invoke.texi: Document -Wexceptions.
>
> gcc/testsuite/ChangeLog:
>
> PR c++/97675
> * g++.old-deja/g++.eh/catch10.C: Adjust dg-warning.
> * g++.dg/warn/Wexceptions1.C: New test.
> * g++.dg/warn/Wexceptions2.C: New test.
> ---
> gcc/c-family/c.opt | 4 ++++
> gcc/cp/except.c | 9 ++++-----
> gcc/doc/invoke.texi | 8 +++++++-
> gcc/testsuite/g++.dg/warn/Wexceptions1.C | 9 +++++++++
> gcc/testsuite/g++.dg/warn/Wexceptions2.C | 10 ++++++++++
> gcc/testsuite/g++.old-deja/g++.eh/catch10.C | 4 ++--
> 6 files changed, 36 insertions(+), 8 deletions(-)
> create mode 100644 gcc/testsuite/g++.dg/warn/Wexceptions1.C
> create mode 100644 gcc/testsuite/g++.dg/warn/Wexceptions2.C
>
> diff --git a/gcc/c-family/c.opt b/gcc/c-family/c.opt
> index 426636be839..9493acb82ff 100644
> --- a/gcc/c-family/c.opt
> +++ b/gcc/c-family/c.opt
> @@ -579,6 +579,10 @@ Werror-implicit-function-declaration
> C ObjC RejectNegative Warning Alias(Werror=, implicit-function-
> declaration)
> This switch is deprecated; use -Werror=implicit-function-declaration
> instead.
>
> +Wexceptions
> +C++ ObjC++ Var(warn_exceptions) Init(1)
> +Warn when an exception handler is shadowed by another handler.
> +
> Wextra
> C ObjC C++ ObjC++ Warning
> ; in common.opt
> diff --git a/gcc/cp/except.c b/gcc/cp/except.c
> index cb1a4105dae..985206f6a64 100644
> --- a/gcc/cp/except.c
> +++ b/gcc/cp/except.c
> @@ -975,11 +975,10 @@ check_handlers_1 (tree master,
> tree_stmt_iterator i)
> tree handler = tsi_stmt (i);
> if (TREE_TYPE (handler) && can_convert_eh (type, TREE_TYPE
> (handler)))
> {
Can you add an auto_diagnostic_group here please.
> - warning_at (EXPR_LOCATION (handler), 0,
> - "exception of type %qT will be caught",
> - TREE_TYPE (handler));
> - warning_at (EXPR_LOCATION (master), 0,
> - " by earlier handler for %qT", type);
> + if (warning_at (EXPR_LOCATION (handler), OPT_Wexceptions,
> + "exception of type %qT will be caught by
> earlier "
> + "handler", TREE_TYPE (handler)))
> + inform (EXPR_LOCATION (master), "for type %qT", type);
> break;
> }
> }
Thanks
Dave
next prev parent reply other threads:[~2020-11-05 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 16:03 Marek Polacek
2020-11-05 20:46 ` Jason Merrill
2020-11-05 23:13 ` David Malcolm [this message]
2020-11-05 23:26 ` Marek Polacek
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=42878a70b164a5a67ac9f3456ec1adbe25e315e9.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=polacek@redhat.com \
/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).