public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/31952] parameters may be redeclared in a function try-block
Date: Mon, 20 Aug 2012 10:30:00 -0000 [thread overview]
Message-ID: <bug-31952-4-vxZGX5wUxy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31952-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31952
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|gcc-bugs at gcc dot gnu.org |janis at gcc dot gnu.org
--- Comment #6 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-08-20 10:29:11 UTC ---
Comment #2 is PR5605.
Comparing to Janis' fix for PR2288
(http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00838.html) looks like the
pushdecl_maybe_friend_1 checks must be beefed up, maybe we need an additional
sk_* for Comment #2. Seems doable.
Adding Janis in CC in case she wants to beat me (or somebody else) on this.
next parent reply other threads:[~2012-08-20 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31952-4@http.gcc.gnu.org/bugzilla/>
2012-08-20 10:30 ` paolo.carlini at oracle dot com [this message]
2012-08-20 10:43 ` paolo.carlini at oracle dot com
2013-05-13 19:29 ` paolo.carlini at oracle dot com
2013-05-14 15:55 ` jason at gcc dot gnu.org
2013-05-15 16:11 ` paolo.carlini at oracle dot com
2007-05-16 13:13 [Bug c++/31952] New: " andrew dot stubbs at st dot com
2007-05-16 19:47 ` [Bug c++/31952] " fang at csl dot cornell dot edu
2007-05-17 14:35 ` andrew dot stubbs at st dot com
2007-05-17 14:52 ` bangerth at dealii dot org
2007-11-01 18:15 ` andrew dot stubbs at st dot com
2009-11-06 6:58 ` pi3orama at gmail 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=bug-31952-4-vxZGX5wUxy@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).