public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/25342] [4.0 Regression] internal compiler error: in lookup_member, at cp/search.c:1209
Date: Fri, 04 Aug 2006 21:17:00 -0000 [thread overview]
Message-ID: <20060804211714.8810.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25342-8718@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from reichelt at gcc dot gnu dot org 2006-08-04 21:17 -------
The reduced testcase from comment #1 now compiles on the 4.0 branch.
However, the original testcase still causes hiccups (but no ICE):
bug.cc: In static member function 'static void
tpl_seq_search<eval>::range<first, last>::find() [with typename eval::enum_type
first = 498, typename eval::enum_type last = 20, eval = xxx]':
bug.cc:10: error: template instantiation depth exceeds maximum of 500 (use
-ftemplate-depth-NN to increase the maximum) instantiating 'struct
tpl_seq_search<xxx>::range<499, 20>'
bug.cc:10: instantiated from 'static void tpl_seq_search<eval>::range<first,
last>::find() [with typename eval::enum_type first = 498, typename
eval::enum_type last = 20, eval = xxx]'
bug.cc:10: instantiated from 'static void tpl_seq_search<eval>::range<first,
last>::find() [with typename eval::enum_type first = 497, typename
eval::enum_type last = 20, eval = xxx]'
[snip]
bug.cc:10: instantiated from 'static void tpl_seq_search<eval>::range<first,
last>::find() [with typename eval::enum_type first = 1, typename
eval::enum_type last = 20, eval = xxx]'
bug.cc:10: instantiated from 'static void tpl_seq_search<eval>::range<first,
last>::find() [with typename eval::enum_type first = 0, typename
eval::enum_type last = 20, eval = xxx]'
bug.cc:28: instantiated from 'void tpl_seq_search_from_to() [with eval = xxx,
typename eval::enum_type first = 0, typename eval::enum_type last = 20]'
bug.cc:40: instantiated from here
bug.cc:10: error: incomplete type 'tpl_seq_search<xxx>::range<499, 20>' used in
nested name specifier
--
reichelt at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25342
next prev parent reply other threads:[~2006-08-04 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 23:57 [Bug c++/25342] New: " jkherciueh at gmx dot net
2005-12-11 0:31 ` [Bug c++/25342] [3.4/4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2005-12-11 5:47 ` mmitchel at gcc dot gnu dot org
2005-12-12 2:45 ` pinskia at gcc dot gnu dot org
2005-12-19 19:26 ` mmitchel at gcc dot gnu dot org
2006-01-14 6:01 ` pinskia at gcc dot gnu dot org
2006-01-16 20:34 ` janis at gcc dot gnu dot org
2006-02-01 2:51 ` mmitchel at gcc dot gnu dot org
2006-02-01 2:55 ` mmitchel at gcc dot gnu dot org
2006-02-01 2:56 ` [Bug c++/25342] [3.4/4.0 " mmitchel at gcc dot gnu dot org
2006-03-11 3:21 ` mmitchel at gcc dot gnu dot org
2006-08-04 21:17 ` reichelt at gcc dot gnu dot org [this message]
2006-08-04 21:40 ` [Bug c++/25342] [4.0 " reichelt at gcc dot gnu dot org
2007-02-03 16:07 ` gdr 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=20060804211714.8810.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).