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 Regression] placement new does not change the dynamic type as it should
- From: "mark at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Oct 2006 16:13:34 -0000
- Subject: [Bug libstdc++/29286] [4.0/4.1/4.2 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 #20 from mark at codesourcery dot com 2006-10-03 16:13 -------
Subject: Re: [4.0/4.1/4.2 Regression] placement new
does not change the dynamic type as it should
ian at airs dot com wrote:
> Fortunately I believe that in a correct program we only have a problem when we
> can actually see the placement new (can any disprove that)? I personally don't
> have a problem with saying that placement new is special. When placement new
> is used, it has to move the pointer into alias set 0.
What about in C, as opposed to C++?
I agree that the obvious special cases are access through char*, arrays
of characters, and placement new. But, I'm afraid that there are lots
of other allocation functions out there that are not spelled "operator
new", and requiring decoration for them isn't something that (as far as
I know) other compilers require.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286