This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/29286] [4.0/4.1/4.2/4.3 Regression] placement new does not change the dynamic type as it should
- From: "gdr at cs dot tamu dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 May 2007 22:42:12 -0000
- Subject: [Bug libstdc++/29286] [4.0/4.1/4.2/4.3 Regression] placement new does not change the dynamic type as it should
- References: <bug-29286-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #147 from gdr at cs dot tamu dot edu 2007-05-23 23:42 -------
Subject: Re: [4.0/4.1/4.2/4.3 Regression] placement new does not change the
dynamic type as it should
"mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| Of course, Gaby's memory model doesn't allow this optimization either;
| we have to worry that "a" and "d" are both in some union somewhere.
| That's why Gaby's model is so bad from an optimization point of view; it
A meta comment: I would highly appreciate if you stopped calling it
"Gaby's model".
It is the *current C++ standard object model*. If you don't like it;
that is fine. But, you don't have to like it. (I don't). But,
please don't call it "Gaby's model". The fact that you don't like it
does not suddenly make it not the standard model.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286