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: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 May 2007 19:46:30 -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 #137 from rguenth at gcc dot gnu dot org 2007-05-23 20:46 -------
Created an attachment (id=13607)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13607&action=view)
patch to perserve store ordering in loop load/store motion
<quote>
Gaby's claim is that given an arbitrary
pointer "p", saying:
(int *)p = 3;
is the same as saying:
*(new (p) int) = 3;
That makes life for the optimizers much, much harder.
</quote>
I say so as well (that those are the same), but I don't agree that this
makes life for optimizers much harder.
Anyway, this is a proposed patch for loop load/store motion that fixes the
last posted testcase. Scheduling issues remain.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286