------- Comment #83 from gdr at cs dot tamu dot edu 2007-05-18 14:26 ------- Subject: Re: [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" <[EMAIL PROTECTED]> writes: | The test case in comment #71 doesn't use placement new either. | | This PR was originally about placement new. Yes. | I think there is general agreement | thta placement new needs to avoid aliasing problem. Yes. The intent of placement new is to specify a new dynamic type, and end the lifetime of previous object. This is type safe, beause the "old" object no longer exists. | I don't think there is | general agreement that arbitrary type casting needs to avoid aliasing problems. agree. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286