public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: a-hw@mail.ru, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8860: illegal constructor causes internal compiler error
Date: Sat, 07 Dec 2002 13:21:00 -0000	[thread overview]
Message-ID: <20021207212121.16487.qmail@sources.redhat.com> (raw)

Synopsis: illegal constructor causes internal compiler error

State-Changed-From-To: open->closed
State-Changed-By: reichelt
State-Changed-When: Sat Dec  7 13:21:20 2002
State-Changed-Why:
    Fixed in gcc 3.2.1.
    gcc 3.2.1 and mainline report:
    
    test.cpp: In constructor `Smoother_Lookup<Function>::Smoother_Lookup(int) [with 
       Function = Test]':
    test.cpp:29:   instantiated from here
    test.cpp:15: type `class Smoother_Lookup<Test>' is not a direct base of `
       Smoother_Lookup<Test>'
    test.cpp:15: no matching function for call to `Smoother::Smoother()'
    test.cpp:3: candidates are: Smoother::Smoother(const Smoother&)
    test.cpp:5:                 Smoother::Smoother(int)
    test.cpp:29:   instantiated from here
    test.cpp:16: no matching function for call to `Test::Test(int&)'
    test.cpp:23: candidates are: Test::Test()
    test.cpp:23:                 Test::Test(const Test&)
    test.cpp:16: `generate_n' undeclared in namespace `std'
    
    I checked this on i686-pc-linux-gnu, but since I could reproduce the problem
    with gcc 3.2 on this platform, I assume it is fixed also for the submitters
    platform.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8860


             reply	other threads:[~2002-12-07 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07 13:21 reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-08  6:46 Alex Kunin
2002-12-07  8:16 a-hw

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=20021207212121.16487.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=a-hw@mail.ru \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).