The TBAA side-effects of C++ operator/expression new are still not properly (read: conservatively correct) handled. The current implementation idea of dealing with that in a flow-insensitive way is going to severely pessimize optimization.
See http://gcc.gnu.org/ml/gcc-patches/2009-01/msg01212.html and followups. -- Summary: TBAA side-effects of C++ new still missing Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: wrong-code, alias Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rguenth at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38964
