public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu 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: Fri, 16 Apr 2010 22:24:00 -0000 [thread overview]
Message-ID: <20100416222424.26350.qmail@sourceware.org> (raw)
In-Reply-To: <bug-9335-180@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from manu at gcc dot gnu dot org 2010-04-16 22:24 -------
(In reply to comment #16)
> Created an attachment (id=20403)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20403&action=view) [edit]
> patch to stop error cascade
>
> This patch fixes the repeated error; it turns out I was wrong about this being
> related to default int. Do you want to experiment more with this patch or
> should I just check it in?
>
I still don't understand why this fixes the problem, but whatever. What is the
output with your patch?
Do you think that my patch is to emit "recursively instantiated" would still be
useful in general? Should I submit it properly?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9335
next prev parent reply other threads:[~2010-04-16 22:24 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 [this message]
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
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=20100416222424.26350.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).