public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jbuck@synopsys.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10754: cast-as-lvalue extension breaks valid programs
Date: Mon, 12 May 2003 17:06:00 -0000	[thread overview]
Message-ID: <20030512165607.14136.qmail@sources.redhat.com> (raw)


>Number:         10754
>Category:       c++
>Synopsis:       cast-as-lvalue extension breaks valid programs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Mon May 12 17:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Joe Buck
>Release:        3.2.3, 3.3-pre, 3.4-pre
>Organization:
>Environment:

>Description:
The cast-as-lvalue extension causes g++ to incorrectly resolve
overloaded functions when the argument is a cast.  For example, compile and run the following program:

----------------
#include <iostream>

void foo(int&) {
    std::cout << "foo(int&) called\n";
}

void foo(const int&) {
    std::cout << "foo(const int&) called\n";
}

int main(int, char**) {
    unsigned u = 0;
    foo((int)u);
}
>How-To-Repeat:
Compile the above program, run it, and you'll get the message

foo(int&) called

instead of the correct answer,

foo(const int&) called.

This is broken at least as far back as 2.95.2, however,
2.7.2.1 handles it correctly (if iostream.h is used and
the std:: references are dropped).
>Fix:

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


                 reply	other threads:[~2003-05-12 17:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030512165607.14136.qmail@sources.redhat.com \
    --to=jbuck@synopsys.com \
    --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).