public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104379] [9/10/11 Regression] -Wshadow warning given three times
Date: Wed, 09 Feb 2022 07:18:25 +0000 [thread overview]
Message-ID: <bug-104379-4-P5MElqbs9B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104379-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104379
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 8 Feb 2022, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104379
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Summary|[9/10/11/12 Regression] |[9/10/11 Regression]
> |-Wshadow warning given |-Wshadow warning given
> |three times |three times
>
> --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Fixed on the trunk so far.
>
> Note, GCC 11 and older doesn't have the warning-control.c* infrastructure, so
> all we could do there is TREE_NO_WARNING.
Or warn from a place that doesn't visit this IL N times?
next prev parent reply other threads:[~2022-02-09 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 11:12 [Bug c++/104379] New: [p/10/11/12 " redi at gcc dot gnu.org
2022-02-04 11:13 ` [Bug c++/104379] [9/10/11/12 " redi at gcc dot gnu.org
2022-02-04 11:20 ` redi at gcc dot gnu.org
2022-02-04 11:47 ` rguenth at gcc dot gnu.org
2022-02-04 11:54 ` rguenth at gcc dot gnu.org
2022-02-04 12:06 ` redi at gcc dot gnu.org
2022-02-04 12:07 ` redi at gcc dot gnu.org
2022-02-04 13:29 ` rguenther at suse dot de
2022-02-04 13:32 ` rguenth at gcc dot gnu.org
2022-02-07 14:07 ` jakub at gcc dot gnu.org
2022-02-08 19:18 ` cvs-commit at gcc dot gnu.org
2022-02-08 19:20 ` [Bug c++/104379] [9/10/11 " jakub at gcc dot gnu.org
2022-02-09 7:18 ` rguenther at suse dot de [this message]
2022-05-27 9:47 ` [Bug c++/104379] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug c++/104379] [11 " rguenth 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-104379-4-P5MElqbs9B@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).