public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5050: template instantiation depth exceeds...
Date: Sat, 11 Jan 2003 21:16:00 -0000 [thread overview]
Message-ID: <20030111211601.31375.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5050; it has been noted by GNATS.
>From neroden@twcny.rr.com Mon Jan 13 01:00:41 2003
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, georg.wild@gmx.de,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/5050: template instantiation depth exceeds...
Date: Sat, 11 Jan 2003 16:07:43 -0500
The following testcase fails when compiled with -ftemplate-depth-1 -O2 or
-ftemplate-depth-1 -O1, but not -ftemplate-depth-1 -O0. (It's always OK with
template depth higher than 1).
This is the error message:
----
test.cxx:5: error: template instantiation depth exceeds maximum of 1 (use
-ftemplate-depth-NN to increase the maximum) instantiating `ostream&
ostream::foo(const T&) [with T = int]'
test.cxx:5: instantiated from `ostream& ostream::foo(const T&) [with T =
int]'test.cxx:12: instantiated from here
----
The problem appears to be that the compiler doesn't realize that it's already
instantiated `ostream& ostream::foo(const T&) [with T = int]'. It doesn't
have to instantiate it repeatedly, does it now? At any rate, behaving
differently with optimization is a no-no.
This is the testcase:
----
struct ostream
{
template<class T> ostream& foo( const T & )
{
return *this;
}
};
void foo()
{
ostream os;
(os.foo(1)).foo(2);
}
----
reply other threads:[~2003-01-11 21:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030111211601.31375.qmail@sources.redhat.com \
--to=neroden@twcny.rr.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).