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 20:15:00 -0000 [thread overview]
Message-ID: <bug-64077-4-jxN5UOmAgz@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
Andrew Dixie <gcc at dixie dot net.nz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Andrew Dixie <gcc at dixie dot net.nz> ---
(In reply to Daniel Krügler from comment #3)
Given the reference to core issue 665, I now think the wording and intent of
the standard is clear.
For completeness I've given an example below, but I'm happy this can be closed.
Thanks.
class base { virtual ~base() {} };
class derived : private base {
friend bool t1(derived *);
};
bool t1(derived *x) {
return dynamic_cast<base *>(x) != 0;
}
If the 'accessible' in p5 includes friendships relationships, then the
dynamic_cast should succeed.
If the 'accessible' in p5 requires a public base (like is required by p8), then
the dynamic cast should fail (or be ill-formed).
I think the wording of the standard clearly specifies succeed.
>From gcc-bugs-return-468795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Nov 27 20:31:16 2014
Return-Path: <gcc-bugs-return-468795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20352 invoked by alias); 27 Nov 2014 20:31:16 -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 20327 invoked by uid 48); 27 Nov 2014 20:31:12 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63833] REAL_PIC_OFFSET_TABLE_REGNUM is wrong for x86-64
Date: Thu, 27 Nov 2014 20:31: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: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-63833-4-MvifIc9Unh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63833-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/msg03267.txt.bz2
Content-length: 583
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc833
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-11-27
Target Milestone|--- |5.0
Ever confirmed|0 |1
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
The psABI
http://www.x86-64.org/svn/trunk/x86-64-ABI/
has been fixed.
next prev parent reply other threads:[~2014-11-27 20:15 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
2014-11-27 20:15 ` gcc at dixie dot net.nz [this message]
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-jxN5UOmAgz@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).