public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pzhao at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/30566] -Wshadow warns about clashes between nested function parameters in C++ Date: Fri, 14 May 2010 03:19:00 -0000 [thread overview] Message-ID: <20100514031943.8378.qmail@sourceware.org> (raw) In-Reply-To: <bug-30566-638@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pzhao at gcc dot gnu dot org 2010-05-14 03:19 ------- Subject: Bug 30566 Author: pzhao Date: Fri May 14 03:19:32 2010 New Revision: 159383 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159383 Log: gcc/cp/ 2010-05-14 Shujing Zhao <pearly.zhao@oracle.com> PR c++/30566 * name-lookup.c (pushdecl_maybe_friend): Avoid the warnings about shadowing the outer parameter or variables by the declaration of nested function in nested structure or class. Warn the shadowing by the declaration of nested lambda expression. gcc/testsuite/ 2010-05-14 Shujing Zhao <pearly.zhao@oracle.com> PR c++/30566 * testsuite/g++.dg/warn/Wshadow-4.C: Adjust. * testsuite/g++.dg/warn/Wshadow-5.C: New test. * testsuite/g++.dg/warn/Wshadow-6.C: New test. Added: trunk/gcc/testsuite/g++.dg/warn/Wshadow-5.C trunk/gcc/testsuite/g++.dg/warn/Wshadow-6.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/name-lookup.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/warn/Wshadow-4.C -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30566
next prev parent reply other threads:[~2010-05-14 3:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-23 23:21 [Bug c++/30566] New: " geoffk at gcc dot gnu dot org 2007-02-11 3:57 ` [Bug c++/30566] " bangerth at dealii dot org 2010-05-07 13:57 ` jason at gcc dot gnu dot org 2010-05-14 3:19 ` pzhao at gcc dot gnu dot org [this message] 2010-05-14 9:43 ` paolo dot carlini at oracle dot com
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=20100514031943.8378.qmail@sourceware.org \ --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: linkBe 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).