From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7640 invoked by alias); 16 May 2007 14:37:23 -0000 Received: (qmail 7217 invoked by uid 48); 16 May 2007 14:36:51 -0000 Date: Wed, 16 May 2007 14:37:00 -0000 Message-ID: <20070516143651.7216.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: "rguenth at gcc dot gnu dot org" 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/msg01208.txt.bz2 ------- Comment #74 from rguenth at gcc dot gnu dot org 2007-05-16 15:36 ------- Note that another solution to this whole problem is to record conflicts for all stored-to types that we cannot disambiguate by points-to analysis. This also solves the reading of the standard that allows int i = 1; (float *)&i = 0.0; at RTL expansion time we need to do the same apart from that we don't have points-to information available. The above supports the notion of "re-using memory changes its dynamic type". Which of course gets a little interesting for aggregates that are initialized piece-wise (not that this problem isn't present now). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286