public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94588] Improve redeclared parameter name diagnostic
Date: Tue, 14 Apr 2020 03:12:59 +0000 [thread overview]
Message-ID: <bug-94588-4-tl7CTjpyhW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94588-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94588
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:
https://gcc.gnu.org/g:7eee265e6bd58bf48da70fef97f2ac7179a9f41c
commit r10-7709-g7eee265e6bd58bf48da70fef97f2ac7179a9f41c
Author: Marek Polacek <polacek@redhat.com>
Date: Mon Apr 13 19:06:39 2020 -0400
c++: Improve redeclared parameter name diagnostic [PR94588]
While reviewing [basic.scope.param] I noticed we don't show the location
of the previous declaration when giving an error about "A parameter name
shall not be redeclared in the outermost block of the function definition".
PR c++/94588
* name-lookup.c (check_local_shadow): Add an inform call.
* g++.dg/diagnostic/redeclaration-1.C: Add dg-message.
next prev parent reply other threads:[~2020-04-14 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 22:56 [Bug c++/94588] New: " mpolacek at gcc dot gnu.org
2020-04-13 22:57 ` [Bug c++/94588] " mpolacek at gcc dot gnu.org
2020-04-13 23:01 ` mpolacek at gcc dot gnu.org
2020-04-14 3:12 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-14 3:13 ` mpolacek 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-94588-4-tl7CTjpyhW@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).