From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12187 invoked by alias); 15 Apr 2005 13:37:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 12125 invoked by uid 48); 15 Apr 2005 13:37:16 -0000 Date: Fri, 15 Apr 2005 13:37:00 -0000 Message-ID: <20050415133716.12124.qmail@sourceware.org> From: "pinskia at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050415124156.21046.tkoenig@gcc.gnu.org> References: <20050415124156.21046.tkoenig@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/21046] move memory allocation out of a loop X-Bugzilla-Reason: CC X-SW-Source: 2005-04/txt/msg02062.txt.bz2 List-Id: ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-15 13:37 ------- (In reply to comment #1) > I would think this is much more easily done in the frontend itself, which has a > higher level representation so that it is much easier to hoist and reuse > allocations. Not really true anymore. Confirmed, related to PR 19831. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |missed-optimization Last reconfirmed|0000-00-00 00:00:00 |2005-04-15 13:37:14 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21046