public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-gnats@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: c++/10381: [3.4 regression] Accepts call to inexistent function
Date: Fri, 11 Apr 2003 19:46:00 -0000	[thread overview]
Message-ID: <20030411194054.4900.qmail@sources.redhat.com> (raw)


>Number:         10381
>Category:       c++
>Synopsis:       [3.4 regression] Accepts call to inexistent function
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 11 19:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Bangerth
>Release:        unknown-1.0
>Organization:
>Environment:
mainline (3.4)
>Description:
This is actually almost unbelievable: present 3.4 accepts
this code:
-----------------------------
struct X {};

template <int>
struct Base {
    static void foo () {
      X::NONEXISTENT ();
    }
};

int main () {
  Base<2>::foo ();
}
-----------------------------
Note the call to the nonexistent member function of X. What
is worse: it doesn't even generate a linker error, it just
ignores the call in the front end. I stumbled upon this
because I mistyped the name of a function, and was wondering
why the call to it had no effect -- very, very deceiving.
The program can be linked and run, by the way, but doesn't
do anything useful.

Mark, I CC: you because this might be cause by the two-stage
name lookup, but I'm in no way sure whether that's the case.
I would really love to see this being fixed quickly, since
it's so mean and can take you a long time to find...

W.
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2003-04-11 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 19:46 bangerth [this message]
2003-04-11 23:05 bangerth
2003-04-15 20:25 mmitchel

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=20030411194054.4900.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=mark@codesourcery.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).