public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: giovannibajo@libero.it
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	sebor@roguewave.com
Subject: Re: c++/10690: bogus ambiguity on templates overloaded on return type
Date: Thu, 08 May 2003 19:56:00 -0000	[thread overview]
Message-ID: <20030508195608.6446.qmail@sources.redhat.com> (raw)

Synopsis: bogus ambiguity on templates overloaded on return type

State-Changed-From-To: open->analyzed
State-Changed-By: bajo
State-Changed-When: Thu May  8 19:56:08 2003
State-Changed-Why:
    Using __PRETTY_FUNCTION__, the code compiles correctly on
    both 3.3 and 3.4 (CVS 20030503). Thus, the bug is more like this:
    
    
    ---------------------------------------
    #include <typeinfo>
    
    template <int VAL>
    void func(void) {}
    
    void foo(void)
    {
        typeid(func<10>);
    }
    ---------------------------------------
    pr10690.cpp: In function `void foo()':
    pr10690.cpp:8: error: insufficient contextual information to determine type
    
    I believe the code should compile (see also DR115, even if
    it does not take into account typeid() but only situations
    where the overload set must decay to function pointer). It
    works with the EDG frontend but not with MSVC7.

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


             reply	other threads:[~2003-05-08 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 19:56 giovannibajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 20:56 Martin Sebor
2003-05-08 18:46 sebor

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=20030508195608.6446.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=sebor@roguewave.com \
    /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).