public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Stefan Rupp <stefan.rupp@inform-ac.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9966: basic_string::operator+ uses recursice template instantiation
Date: Wed, 05 Mar 2003 15:56:00 -0000	[thread overview]
Message-ID: <20030305155601.16006.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9966; it has been noted by GNATS.

From: Stefan Rupp <stefan.rupp@inform-ac.com>
To: gcc-gnats@gcc.gnu.org,  gcc-bugs@gcc.gnu.org,  nobody@gcc.gnu.org, 
 gcc-prs@gcc.gnu.org,  struppi@acm.org
Cc:  
Subject: Re: c++/9966: basic_string::operator+ uses recursice template instantiation
Date: Wed, 05 Mar 2003 16:52:59 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9966
 
 The question may be a different one:
 
 Is an implementation forced to use such a huge template-depth for 
 compiling the expression in question, so that a template-depth of more 
 than 17 is neccessary, or is it just the GNU string implementation which 
 makes it neccessary for the compiler to have a huge (default) 
 template-depth of 500 (btw. I did not find the defaukt value in the gcc 
 info pages; the only number noted there is the 17 from the ISO standard)?
 
 In the former case the limitation of 17 in the ISO standard is nonsense, 
 in the latter case, the GNU string implementation may be broken.
 
 Since I don't know very much about the internals of the GNU string 
 implementation, any input is welcome.
 


             reply	other threads:[~2003-03-05 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 15:56 Stefan Rupp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-05 15:06 bangerth
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=20030305155601.16006.qmail@sources.redhat.com \
    --to=stefan.rupp@inform-ac.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).