public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, struppi@acm.org Subject: Re: c++/9966: basic_string::operator+ uses recursice template instantiation Date: Wed, 05 Mar 2003 15:06:00 -0000 [thread overview] Message-ID: <20030305150622.20522.qmail@sources.redhat.com> (raw) Synopsis: basic_string::operator+ uses recursice template instantiation State-Changed-From-To: open->closed State-Changed-By: bangerth State-Changed-When: Wed Mar 5 15:06:21 2003 State-Changed-Why: This is not a bug: the default for -ftemplate-depth is 500, so if you arbitrarily restrict it you might expect trouble. The standard prescribes the rather limited minimum of 17 for -ftemplate-depth, which apparently is not enough to compile some useful programs (like yours). W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9966
next reply other threads:[~2003-03-05 15:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-05 15:06 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-05 15:56 Stefan Rupp 2003-03-05 14:16 struppi
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=20030305150622.20522.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=struppi@acm.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).