From: Jason Merrill <jason@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Guenther <rguenther@suse.de>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH, PR 45934 4/6] Dynamic type change detection
Date: Fri, 03 Dec 2010 16:07:00 -0000 [thread overview]
Message-ID: <4CF915AA.4040706@redhat.com> (raw)
In-Reply-To: <20101203134515.GB3371@virgil.arch.suse.de>
On 12/03/2010 08:45 AM, Martin Jambor wrote:
> On Thu, Dec 02, 2010 at 06:25:28PM -0500, Jason Merrill wrote:
>> On 12/01/2010 03:16 PM, Martin Jambor wrote:
>>> and there are no unions of non-POD types
>>
>> This is actually no longer true in C++0x.
>
> OK... but from what I have googled I understand that types with
> virtual functions are still explicitly not allowed to be fields of
> a union, right?
They are allowed now. 9.5/4 of N3126:
[ Example: Consider an object u of a union type U having non-static data
members m of type M and n of type N. If M has a non-trivial destructor
and N has a non-trivial constructor (for instance, if they declare or
inherit virtual functions), the active member of u can be safely
switched from m to n using the destructor and placement new operator as
follows:
u.m.~M();
new (&u.n) N;
-- end example ]
I wouldn't worry about this for now, though. I'll add it to the pile of
union language issues.
Jason
next prev parent reply other threads:[~2010-12-03 16:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 20:22 [PATCH, PR 45934 0/6] Devirtualization aware of dynamic type changes Martin Jambor
2010-12-01 20:22 ` [PATCH, PR 45934 3/6] More robust compute_complex_ancestor_jump_func Martin Jambor
2010-12-01 20:28 ` Richard Guenther
2010-12-01 20:23 ` [PATCH, PR 45934 2/6] Remove devirtualizations that cannot be done Martin Jambor
2010-12-01 20:35 ` Richard Guenther
2010-12-02 10:46 ` Martin Jambor
2010-12-02 12:14 ` Richard Guenther
2010-12-01 20:23 ` [PATCH, PR 45934 5/6] Identify the new dynamic type after change Martin Jambor
2010-12-01 20:23 ` [PATCH, PR 45934 1/6] [PR 46287] Do not generate direct calls to thunks Martin Jambor
2010-12-01 20:58 ` Jan Hubicka
2010-12-03 13:01 ` Martin Jambor
2010-12-14 17:39 ` Jan Hubicka
2010-12-15 15:15 ` Martin Jambor
2010-12-15 15:46 ` Jan Hubicka
2010-12-15 16:52 ` Martin Jambor
2010-12-17 14:14 ` H.J. Lu
2010-12-01 20:23 ` [PATCH, PR 45934 6/6] Intraprocedural type-based devirtualization Martin Jambor
2010-12-02 15:40 ` Richard Guenther
2010-12-01 20:23 ` [PATCH, PR 45934 4/6] Dynamic type change detection Martin Jambor
2010-12-02 15:19 ` Richard Guenther
2010-12-02 16:17 ` Richard Guenther
2010-12-09 11:30 ` Martin Jambor
2010-12-02 23:25 ` Jason Merrill
2010-12-03 13:45 ` Martin Jambor
2010-12-03 14:34 ` Gabriel Dos Reis
2010-12-03 16:07 ` Jason Merrill [this message]
2010-12-03 16:09 ` Richard Guenther
2010-12-03 16:21 ` Gabriel Dos Reis
2010-12-04 23:14 ` Jason Merrill
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=4CF915AA.4040706@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
/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).