public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52458] [c++0x] compiler fails on for(:*this) with non-public inheritance with message: Internal compiler error: Error reporting routines re-entered.
Date: Fri, 02 Mar 2012 17:07:00 -0000 [thread overview]
Message-ID: <bug-52458-4-kbFFm4euzC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52458-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52458
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-02 17:06:57 UTC ---
(In reply to comment #5)
> but this was a bug so I post it. It's pity MinGW updated only to 4.6.2.
The newest GCC release, 4.6.3, was only released yesterday!
next prev parent reply other threads:[~2012-03-02 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 2:17 [Bug c++/52458] New: " crimaniak at gmail dot com
2012-03-02 2:19 ` [Bug c++/52458] " crimaniak at gmail dot com
2012-03-02 9:36 ` redi at gcc dot gnu.org
2012-03-02 10:35 ` redi at gcc dot gnu.org
2012-03-02 12:39 ` redi at gcc dot gnu.org
2012-03-02 14:50 ` crimaniak at gmail dot com
2012-03-02 17:07 ` redi at gcc dot gnu.org [this message]
2012-10-04 12:14 ` paolo.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=bug-52458-4-kbFFm4euzC@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).