public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/9335] repeated diagnostic when maximum template depth is exceeded Date: Sat, 17 Apr 2010 03:53:00 -0000 [thread overview] Message-ID: <20100417035328.29241.qmail@sourceware.org> (raw) In-Reply-To: <bug-9335-180@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1366 bytes --] ------- Comment #18 from jason at gcc dot gnu dot org 2010-04-17 03:53 ------- The output with my patch is wa.C:2:38: error: template instantiation depth exceeds maximum of 1024 (use -ftemplate-depth= to increase the maximum) instantiating struct X<-0x000000018> wa.C:2:38: instantiated from const int X<-0x000000017>::value wa.C:2:38: instantiated from const int X<-0x000000016>::value wa.C:2:38: instantiated from const int X<-0x000000015>::value wa.C:2:38: instantiated from const int X<-0x000000014>::value wa.C:2:38: instantiated from const int X<-0x000000013>::value wa.C:2:38: [ skipping 1014 instantiation contexts ] wa.C:2:38: instantiated from const int X<996>::value wa.C:2:38: instantiated from const int X<997>::value wa.C:2:38: instantiated from const int X<998>::value wa.C:2:38: instantiated from const int X<999>::value wa.C:2:38: instantiated from const int X<1000>::value wa.C:4:17: instantiated from here wa.C:2:38: error: incomplete type X<-0x000000018> used in nested name specifier it avoids the error cascade by avoiding all the non-constant initializer errors. I guess your patch just cuts down the "instantiated from" list to one element? I think the previous change to skip all but 10 is good enough. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9335
next prev parent reply other threads:[~2010-04-17 3:53 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-9335-180@http.gcc.gnu.org/bugzilla/> 2010-02-18 14:19 ` [Bug c++/9335] Inordinately long output " paolo dot carlini at oracle dot com 2010-02-19 1:49 ` manu at gcc dot gnu dot org 2010-02-19 1:54 ` manu at gcc dot gnu dot org 2010-02-19 1:54 ` paolo dot carlini at oracle dot com 2010-02-19 1:59 ` manu at gcc dot gnu dot org 2010-02-19 2:03 ` manu at gcc dot gnu dot org 2010-02-19 9:16 ` paolo dot carlini at oracle dot com 2010-02-20 1:55 ` [Bug c++/9335] repeated diagnostic " manu at gcc dot gnu dot org 2010-04-13 23:48 ` manu at gcc dot gnu dot org 2010-04-14 1:41 ` jason at gcc dot gnu dot org 2010-04-14 10:10 ` lopezibanez at gmail dot com 2010-04-16 22:07 ` jason at gcc dot gnu dot org 2010-04-16 22:24 ` manu at gcc dot gnu dot org 2010-04-17 3:53 ` jason at gcc dot gnu dot org [this message] 2010-04-17 7:59 ` manu at gcc dot gnu dot org 2010-04-18 14:42 ` jason at gcc dot gnu dot org 2010-04-18 16:17 ` manu at gcc dot gnu dot org 2010-04-18 17:10 ` jason at gcc dot gnu dot org 2010-04-18 17:40 ` manu at gcc dot gnu dot org 2010-04-18 22:35 ` [Bug c++/9335] [4.3/4.4/4.5/4.6 regression] " jason at gcc dot gnu dot org 2010-04-21 6:07 ` jason at gcc dot gnu dot org 2010-04-28 8:34 ` manu at gcc dot gnu dot org 2010-04-28 8:40 ` manu at gcc dot gnu dot org 2010-04-28 18:50 ` jason 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=20100417035328.29241.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: 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).