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,
	levon@movementarian.org, nobody@gcc.gnu.org
Subject: Re: c++/9486: [3.4 regression] can't find a matching member template function
Date: Tue, 28 Jan 2003 19:50:00 -0000	[thread overview]
Message-ID: <20030128195014.26995.qmail@sources.redhat.com> (raw)

Old Synopsis: boost_no_mem_tem_keyword fails with no matching function
New Synopsis: [3.4 regression] can't find a matching member template function

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Jan 28 19:50:14 2003
State-Changed-Why:
    Confirmed. Here's a cut-down:
    ----------------------------
    template <class T> struct X {
       template <class U> void foo(U);
    };
    
    template <class T>
    void bar() {
       X<double> x;
       x.template foo<T>(0);
    }
    template void bar<int>();
    -------------------------
    
    g/a> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c b.c
    b.c: In function `void bar() [with T = int]':
    b.c:10:   instantiated from here
    b.c:8: error: no matching function for call to `X<double>::foo(int)'
    
    This used to work until 3.3.
    
    If one removes the argument of foo but leaves it as a 
    template, one gets an ICE instead. I'll report this in a
    separate PR.
    
    W.

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


             reply	other threads:[~2003-01-28 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 19:50 bangerth [this message]
2003-04-16  1:35 reichelt

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=20030128195014.26995.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=levon@movementarian.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).