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++/8205: [3.2 regression] using declaration & mulitiple inheritance
Date: Fri, 13 Dec 2002 14:06:00 -0000	[thread overview]
Message-ID: <20021213220601.4925.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-bugs@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/8205: [3.2 regression] using declaration & mulitiple
 inheritance
Date: Fri, 13 Dec 2002 16:04:50 -0600 (CST)

 Upon closer inspection, I believe that this high priority regression is 
 actually another manifestation of (high priority regression) c++/8117. The 
 testcase for the latter is 
 ---------------------
 struct A { virtual void foo() = 0; };
 
 struct B : A {};
 struct C : A {};
 
 struct D : B, C { virtual void foo() {} };
 
 void (D::* p)() = &D::foo;  // 'A' is an ambiguous base of 'D'
 --------------------
 while for the former
 --------------------
 struct A { int i; };
 struct B {};
 class E : A, B { public: using A::i; };
 
 void foo() { E().i; } // "`A' is an inaccessible base of `E'"
 ---------------------
 
 The theory that they are the same is also supported by the fact that both 
 started to show up somewhere between 2001-11-25 and 2001-12-01.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-12-13 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13 14:06 Wolfgang Bangerth [this message]
2002-12-23  9:46 Janis Johnson
2003-04-25 21:00 jbuck

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=20021213220601.4925.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).