public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ctron@dentrassi.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/10600: method lookup does not work correctly in dervied classes with virtual methods
Date: Fri, 02 May 2003 08:36:00 -0000 [thread overview]
Message-ID: <20030502082105.29402.qmail@sources.redhat.com> (raw)
>Number: 10600
>Category: c++
>Synopsis: method lookup does not work correctly in dervied classes with virtual methods
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Fri May 02 08:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ctron@dentrassi.de
>Release: gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
>Organization:
>Environment:
REDHAT 9
>Description:
See the attachments. The section "Problem" should work but does not.
>How-To-Repeat:
compile section "Problem" of the attachment
>Fix:
Use the workaround of the section "Workaround" in the attachment
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="inh_1.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="inh_1.cc"
Ci8vIC0tLS0tLS0tLT4+Pj4+Pj4+Pj4+PiBQcm9ibGVtCgojaW5jbHVkZSA8aW9zdHJlYW0+Cgpj
bGFzcyBBIHsKcHVibGljOgogIHZpcnR1YWwgdm9pZCB0ZXN0ICggdm9pZCApID0gMDsKfTsKCmNs
YXNzIEIgOiBwdWJsaWMgQSB7CnB1YmxpYzoKICB2aXJ0dWFsIHZvaWQgdGVzdCAoIHZvaWQgKQog
IHsKICAgIHRlc3QgKCAxICk7CiAgfQogIHZpcnR1YWwgdm9pZCB0ZXN0ICggaW50IGkgKSA9IDA7
Cn07CgpjbGFzcyBDIDogcHVibGljIEIgewpwdWJsaWM6CiAgdmlydHVhbCB2b2lkIHRlc3QgKCBp
bnQgaSApCiAgewogICAgc3RkOjpjb3V0IDw8ICJpID0gIiA8PCBpIDw8IHN0ZDo6ZW5kbDsKICB9
Cn07CgppbnQgbWFpbiAoIGludCBhcmdjLCBjaGFyICogYXJndltdICkKewogIEMgYzsKICBjLnRl
c3QgKCk7Cn0KCi8vIC0tLS0tLS0tLT4+Pj4+Pj4+Pj4+PiBXb3JrYXJvdW5kCgoKI2luY2x1ZGUg
PGlvc3RyZWFtPgoKY2xhc3MgQSB7CnB1YmxpYzoKICB2aXJ0dWFsIHZvaWQgdGVzdCAoIHZvaWQg
KSA9IDA7Cn07CgpjbGFzcyBCIDogcHVibGljIEEgewpwdWJsaWM6CiAgdmlydHVhbCB2b2lkIHRl
c3QgKCB2b2lkICkKICB7CiAgICB0ZXN0XzEgKCAxICk7CiAgfQogIHZpcnR1YWwgdm9pZCB0ZXN0
XzEgKCBpbnQgaSApID0gMDsKfTsKCmNsYXNzIEMgOiBwdWJsaWMgQiB7CnB1YmxpYzoKICB2aXJ0
dWFsIHZvaWQgdGVzdF8xICggaW50IGkgKQogIHsKICAgIHN0ZDo6Y291dCA8PCAiaSA9ICIgPDwg
aSA8PCBzdGQ6OmVuZGw7CiAgfQp9OwoKaW50IG1haW4gKCBpbnQgYXJnYywgY2hhciAqIGFyZ3Zb
XSApCnsKICBDIGM7CiAgYy50ZXN0ICgpOwp9Cg==
next reply other threads:[~2003-05-02 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 8:36 ctron [this message]
2003-05-02 10:29 giovannibajo
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=20030502082105.29402.qmail@sources.redhat.com \
--to=ctron@dentrassi.de \
--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).