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: Sun, 18 Apr 2010 17:10:00 -0000	[thread overview]
Message-ID: <20100418170946.22977.qmail@sourceware.org> (raw)
In-Reply-To: <bug-9335-180@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from jason at gcc dot gnu dot org  2010-04-18 17:09 -------
(In reply to comment #21)
> Is that ok or you would prefer the following?
> 
> /home/manuel/src/pr9335.C:2:36: error: template instantiation depth exceeds
> maximum of 1024 (use -ftemplate-depth= to increase the maximum) instantiating
> 'struct X<-0x00000000000000018>'
> /home/manuel/src/pr9335.C:2:36:   recursively instantiated from 'const int
> X<N-1>::value'
> /home/manuel/src/pr9335.C:2:36:   recursively instantiated from 'const int
> X<1000>::value'
> /home/manuel/src/pr9335.C:4:17:   instantiated from here

I was thinking just

/home/manuel/src/pr9335.C:2:36:   recursively instantiated from 'const int
X<999>::value'
/home/manuel/src/pr9335.C:2:36:   instantiated from 'const int X<1000>::value'

I think seeing one iteration would make it clearer.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9335


  parent reply	other threads:[~2010-04-18 17:10 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
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 [this message]
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=20100418170946.22977.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).