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: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 May 2007 17:01:58 -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 #76 from ian at airs dot com 2007-05-16 18:01 -------
I don't believe that the C++ standards writers really meant to eliminate TBAA.
And that is the inevitable consequence of the dynamic memory type approach if
you are allowed to change the dynamic type in a function.
If we really want to adopt that approach, then the simple fix is for the C++
frontend to set flag_strict_aliasing to 0. But I don't think we want to do
that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286