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:57:57 -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 #150 from gdr at cs dot tamu dot edu 2007-05-23 23:57 -------
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:
| Subject: Re: [4.0/4.1/4.2/4.3 Regression] placement
| new does not change the dynamic type as it should
|
| joseph at codesourcery dot com wrote:
|
| > DR#236 <http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_236.htm> was
| > what eventually said for C that you don't need to worry about that; I'd
| > think the aim should be to get C++ to agree with that ruling.
|
| Thank you for the pointer. That seems directly on point, and makes C99
| match the existing GCC practice: we don't need to worry that pointers
| might point to unions.
|
| Gaby, would you please forward that to the C++ reflector, so that the
| reflector has that information as well? They should be aware that the
| model you're proposing is at odds with C99.
|
Yes, I'll right now.
Since I brought upt this issue, Nick MacLaren sent me a note he had
circulated about these very issues on C99. It is also being discussed
on the -core reflector.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286