[Bug libstdc++/29286] [4.0/4.1/4.2/4.3 Regression] placement new does not change the dynamic type as it should

[ian at airs dot com]

------- Comment #79 from ian at airs dot com  2007-05-18 07:25 -------
The test case in comment #71 doesn't use placement new either.

This PR was originally about placement new.  I think there is general agreement
thta placement new needs to avoid aliasing problem.  I don't think there is
general agreement that arbitrary type casting needs to avoid aliasing problems.
Have you found any problems with my most recent patch and placement new?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286