public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: martin@xemacs.org
To: gcc-gnats@gcc.gnu.org
Subject: c++/9126: g++ incorrectly prefers non-template user-defined conversion operator
Date: Thu, 02 Jan 2003 10:16:00 -0000	[thread overview]
Message-ID: <20030102100650.28089.qmail@sources.redhat.com> (raw)


>Number:         9126
>Category:       c++
>Synopsis:       g++ incorrectly prefers non-template user-defined conversion operator
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 02 02:16:02 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Martin Buchholz
>Release:        gcc-3.2
>Organization:
>Environment:
Linux x86
>Description:
When a function has both an "ordinary" user-defined
conversion operator and a templated one, the
ordinary one should be preferred, but only if
there is no other reason to prefer the templated one.

In the example below, the conversion operator template
specialized for "long" is an exact match for the call to f.

So the argument for f should be provided by
the instantiation of the template with "long".

With g++, the program exits with return code 1.
With icc (and likely Comeau C++), the program exits
with return code 0.

-----------------------------------------

struct C
{
  inline operator int () { return 1; }
  template <class T> inline operator T () { return 0; }
};

inline long f (long x) { return x; }

int
main (int argc, char *argv[])
{
  return f (C ());
}
>How-To-Repeat:
Put code into "file.cc" and then:
g++ file.cc && ./a.out; echo $?   ==> exit status 1
icc file.cc && ./a.out; echo $?   ==> exit status 0
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-02 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 10:16 martin [this message]
2003-01-07 23:40 bangerth

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=20030102100650.28089.qmail@sources.redhat.com \
    --to=martin@xemacs.org \
    --cc=gcc-gnats@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).