From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7114 invoked by alias); 4 Jun 2008 16:48:55 -0000 Received: (qmail 5347 invoked by uid 48); 4 Jun 2008 16:48:13 -0000 Date: Wed, 04 Jun 2008 16:48:00 -0000 Message-ID: <20080604164813.5346.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/23383] builtin array operator new is not marked with malloc attribute In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "davidxl 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: 2008-06/txt/msg00167.txt.bz2 ------- Comment #13 from davidxl at gcc dot gnu dot org 2008-06-04 16:48 ------- (In reply to comment #12) > Interesting things start to happen once you inline allocator functions as well. > See PR29286 and PR33407 which we still don't handle 100% correct. > I browsed through the two bugs -- it seems that compiler should get this right regardless -- local pointer analysis should detect the must aliasing and should overrule the type based aliasing decision when the placement new is inlined. If not inlined, compiler should know the exact semantics of placement new (return == arg), or treat it conservatively. David -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23383