public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at dixie dot net.nz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64077] dynamic_cast incorrectly rejected for private base
Date: Thu, 27 Nov 2014 07:59:00 -0000	[thread overview]
Message-ID: <bug-64077-4-nnkoquVm6r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64077-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64077

--- Comment #2 from Andrew Dixie <gcc at dixie dot net.nz> ---
(In reply to Daniel Krügler from comment #1)

Thanks for investigating and providing the reference.

I did not understand that upcasts were intended to override potential cross
casts, issue 665 makes this clear.

I agree the testcase is invalid.

In p5, is "inaccessible" meant to include friendship relationships granted by
the current scope or instead use the explicit public base rules spelt out in
p8?

The second part of the patch was implementing the latter, but I now also think
this is invalid.
>From gcc-bugs-return-468730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Nov 27 08:35:27 2014
Return-Path: <gcc-bugs-return-468730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6917 invoked by alias); 27 Nov 2014 08:35:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6877 invoked by uid 48); 27 Nov 2014 08:35:19 -0000
From: "manfred.rudigier at omicron dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62231] Exception handling broken on powerpc-e500v2-linux-gnuspe
Date: Thu, 27 Nov 2014 08:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: manfred.rudigier at omicron dot at
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-62231-4-UeB2oDcZOY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-62231-4@http.gcc.gnu.org/bugzilla/>
References: <bug-62231-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg03202.txt.bz2
Content-length: 260

https://gcc.gnu.org/bugzilla/show_bug.cgi?idb231

--- Comment #2 from manfred.rudigier at omicron dot at ---
I've built 4.9.2 today and can also confirm that it is working with this
version, so it seems the bug has already been fixed in newer GCC versions.


  parent reply	other threads:[~2014-11-27  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 22:58 [Bug c++/64077] New: " gcc at dixie dot net.nz
2014-11-26 20:31 ` [Bug c++/64077] " daniel.kruegler at googlemail dot com
2014-11-27  7:59 ` gcc at dixie dot net.nz [this message]
2014-11-27 20:15 ` gcc at dixie dot net.nz
2014-11-27 21:05 ` daniel.kruegler at googlemail dot com

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=bug-64077-4-nnkoquVm6r@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).