From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21498 invoked by alias); 16 May 2007 17:02:16 -0000 Received: (qmail 21442 invoked by uid 48); 16 May 2007 17:01:58 -0000 Date: Wed, 16 May 2007 17:02:00 -0000 Message-ID: <20070516170158.21441.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/29286] [4.0/4.1/4.2/4.3 Regression] placement new does not change the dynamic type as it should In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ian at airs dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-05/txt/msg01222.txt.bz2 ------- Comment #76 from ian at airs dot com 2007-05-16 18:01 ------- I don't believe that the C++ standards writers really meant to eliminate TBAA. And that is the inevitable consequence of the dynamic memory type approach if you are allowed to change the dynamic type in a function. If we really want to adopt that approach, then the simple fix is for the C++ frontend to set flag_strict_aliasing to 0. But I don't think we want to do that. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286