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++/13289] [3.3/3.4 regression] ICE in regenerate_decl_from_template on recursive template Date: Thu, 04 Dec 2003 17:26:00 -0000 [thread overview] Message-ID: <20031204172650.4415.qmail@sources.redhat.com> (raw) In-Reply-To: <20031203235040.13289.gianni@mariani.ws> ------- Additional Comments From reichelt at gcc dot gnu dot org 2003-12-04 17:26 ------- First, here's a slightly different example that triggers the ICE: ============================================================== template <int> struct A { static const int i; }; template <int N> const int A<N>::i = ( N ? A<N&0>::i : 0 ); int j=A<1>::i; ============================================================== x.cc: In instantiation of `const int A<0>::i': x.cc:10: instantiated from `const int A<0>::i' x.cc:10: instantiated from `const int A<1>::i' x.cc:12: instantiated from here x.cc:10: internal compiler error: in regenerate_decl_from_template, at cp/pt.c:10771 Please submit a full bug report, [etc.] If I replace "N&0" by "0" in the example above, I get the following error message: x.cc:10: error: template instantiation depth exceeds maximum of 500 (use -ftemplate-depth-NN to increase the maximum) instantiating `A<0>::i' x.cc:10: instantiated from `const int A<0>::i' [repeated ~1000 times] x.cc:12: instantiated from here Second, I don't agree with Wolfgang. This code looks valid to me (and is accepted by gcc 3.0 - 3.2.3 as well as icc 7 and Comeau). Thus, we have a regression here and therefore severity "critical". -- What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |critical Summary|ICE in |[3.3/3.4 regression] ICE in |regenerate_decl_from_templat|regenerate_decl_from_templat |e on recursive template |e on recursive template http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13289
next prev parent reply other threads:[~2003-12-04 17:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-03 23:50 [Bug c++/13289] New: internal compiler error : regenerate_decl_from_template, at cp/pt.c:10131 gianni at mariani dot ws 2003-12-03 23:54 ` [Bug c++/13289] [3.3/3.4 Regression] " pinskia at gcc dot gnu dot org 2003-12-04 17:11 ` [Bug c++/13289] ICE in regenerate_decl_from_template on recursive template bangerth at dealii dot org 2003-12-04 17:15 ` bangerth at dealii dot org 2003-12-04 17:26 ` reichelt at gcc dot gnu dot org [this message] 2003-12-04 19:54 ` [Bug c++/13289] [3.3/3.4 regression] " bangerth at dealii dot org 2003-12-19 14:39 ` lerdsuwa at gcc dot gnu dot org 2003-12-20 20:35 ` pinskia at gcc dot gnu dot org 2003-12-24 16:21 ` lerdsuwa at gcc dot gnu dot org 2003-12-29 11:35 ` cvs-commit at gcc dot gnu dot org 2003-12-29 11:58 ` lerdsuwa at gcc dot gnu dot org 2004-01-12 20:10 ` cvs-commit at gcc dot gnu dot org 2004-01-12 20:11 ` [Bug c++/13289] [3.3 " pinskia at gcc dot gnu dot org 2004-01-21 3:26 ` cvs-commit at gcc dot gnu dot org 2004-01-21 3:26 ` 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=20031204172650.4415.qmail@sources.redhat.com \ --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).