public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/43069] [4.5 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'overload' in set_decl_namespace, at cp/name-lookup.c:3105
Date: Tue, 16 Feb 2010 22:51:00 -0000 [thread overview]
Message-ID: <20100216225126.3799.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43069-14164@http.gcc.gnu.org/bugzilla/>
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE: tree check: expected |[4.5 Regression] ICE: tree
|tree that contains 'decl |check: expected tree that
|minimal' structure, have |contains 'decl minimal'
|'overload' in |structure, have 'overload'
|set_decl_namespace, at |in set_decl_namespace, at
|cp/name-lookup.c:3105 |cp/name-lookup.c:3105
Target Milestone|--- |4.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43069
next prev parent reply other threads:[~2010-02-16 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 0:51 [Bug c++/43069] New: ICE: tree check: expected tree that contains ‘decl minimal’ structure, have ‘overload’ " zsojka at seznam dot cz
2010-02-16 22:51 ` pinskia at gcc dot gnu dot org [this message]
2010-02-17 3:42 ` [Bug c++/43069] [4.5 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'overload' " hjl dot tools at gmail dot com
2010-02-17 17:34 ` mmitchel at gcc dot gnu dot org
2010-02-17 20:46 ` jason at gcc dot gnu dot org
2010-02-17 22:52 ` jason at gcc dot gnu dot org
2010-02-17 22:57 ` jason at gcc dot gnu dot org
2010-02-23 17:07 ` hjl at gcc dot gnu dot 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=20100216225126.3799.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: 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).