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, mmitchel@gcc.gnu.org,
	nobody@gcc.gnu.org, rguenth@tat.physik.uni-tuebingen.de
Subject: Re: c++/9411: [3.4 regression] [New parser] Template function lookup problem
Date: Thu, 23 Jan 2003 00:32:00 -0000	[thread overview]
Message-ID: <20030123003227.20036.qmail@sources.redhat.com> (raw)

Old Synopsis: Template function lookup problem (new parser)
New Synopsis: [3.4 regression] [New parser] Template function lookup problem

Responsible-Changed-From-To: unassigned->mmitchel
Responsible-Changed-By: bangerth
Responsible-Changed-When: Thu Jan 23 00:32:27 2003
Responsible-Changed-Why:
    He's the new parser man.
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Jan 23 00:32:27 2003
State-Changed-Why:
    Confirmed. Here's a slightly simpler snippet:
    -----------------------
    struct X {
        template <class B> void foo(B);
    };
    
    template <class D>
    void bar() {
      X().foo<D>(1);
    }
    
    template void bar<int> ();
    --------------------------------
    We now get
    g/a> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -c x.cc
    x.cc: In function `void bar() [with D = int]':
    x.cc:10:   instantiated from here
    x.cc:7: error: no matching function for call to `X::foo(int)'
    g/a> /home/bangerth/bin/gcc-3.3-pre/bin/gcc -c x.cc
    
    It works on the 3.3 branch. This should really work, I'd
    guess. Note that using "X().template foo<D>" also does no
    good.
    
    W.

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


             reply	other threads:[~2003-01-23  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23  0:32 bangerth [this message]
2003-04-16 20:07 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=20030123003227.20036.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=mmitchel@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rguenth@tat.physik.uni-tuebingen.de \
    /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).