public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9377: g++ 64bit calls wrong function -> Multi-inheritance: pointer to member function of the 2nd base calss points to wrong place
Date: Tue, 21 Jan 2003 21:36:00 -0000	[thread overview]
Message-ID: <20030121213601.24965.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9377; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Andrew Xiong <axiong@ca.ibm.com>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/9377: g++ 64bit calls wrong function -> Multi-inheritance:
 pointer to member function of the 2nd base calss points to wrong place
Date: Tue, 21 Jan 2003 15:30:10 -0600 (CST)

 Andrew,
 Thanks for the answers.
 
 >         d1ptr = (D*) new B2 ;  //with the cast, we can also do this
 >         printf( "%s\n", (d1ptr->*select(1))() ) ;
 
 This can really only work by chance. By creating a B2 you run code that 
 sets up the virtual function table for a B2, and invoking a function from 
 the D function table will invoke undefined behavior. I also bet that this 
 will not work with virtual inheritance.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 
 


             reply	other threads:[~2003-01-21 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 21:36 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-21 22:26 axiong
2003-01-21 20:56 axiong
2003-01-21 20:06 Janis Johnson
2003-01-21 17:36 Wolfgang Bangerth
2003-01-21 17:27 bangerth
2003-01-21 17:06 axiong
2003-01-21 16:20 bangerth
2003-01-20 19:36 axiong

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=20030121213601.24965.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).