public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8205: [3.2 regression] using declaration & mulitiple inheritance
Date: Mon, 23 Dec 2002 09:46:00 -0000	[thread overview]
Message-ID: <20021223174603.5490.qmail@sources.redhat.com> (raw)

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

From: Janis Johnson <janis187@us.ibm.com>
To: hou_zhenyu@hotmail.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   chicares@mindspring.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/8205: [3.2 regression] using declaration & mulitiple inheritance
Date: Mon, 23 Dec 2002 09:44:31 -0800

 The regression reported in PR c++/8205 still exists on the
 3.2 branch.  The patch that caused the bug to show up, and
 the patch that caused it to go away on the mainline, are
 shown here.  They are both very large so it's quite likely
 that this information isn't very useful.
 
 Here's the patch that caused the regression to show up:
 
 2001-11-25  Nathan Sidwell  <nathan@codesourcery.com>
 
         PR g++/3145
         * class.c
         * cp-tree.h
         * call.c
         * cvt.c
         * init.c
         * rtti.c
         * search.c
         * typeck.c
         * typeck2.c
 
 Here's the patch that caused it to go away on the mainline:
 
 2002-08-07  Mark Mitchell  <mark@codesourcery.com>
 
         Rework build_component_ref.
         * call.c
         * class.c
         * cp-tree.def
         * cp-tree.h
         * decl.c
         * decl2
         * error.c
         * except.c
         * init.c
         * method.c
         * parse.y
         * pt.c
         * search.c
         * semantics.c
         * spew.c
         * tree.c
         * typeck.c
         * typeck2.c
 
 Here's a small test case that causes the compiler to
 complain about valid code on i686-linux with the 3.2
 branch cc1plus:
 
 -------------------
 class A { public: int i; };
 class B {};
 class E : A, B { public: using A::i; };
 
 int main() {
   E e;
   e.i; // "`A' is an inaccessible base of `E'"
 }
 -------------------
 
 Output from the 3.2 branch compiler:
 
 8205.C: In function `int main()':
 8205.C:7: `A' is an inaccessible base of `E'
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8205
 
 
 


             reply	other threads:[~2002-12-23 17:46 UTC|newest]

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

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=20021223174603.5490.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --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).