From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13220 invoked by alias); 20 Dec 2007 00:02:55 -0000 Received: (qmail 13102 invoked by uid 48); 20 Dec 2007 00:02:38 -0000 Date: Thu, 20 Dec 2007 00:02:00 -0000 Message-ID: <20071220000238.13101.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/26854] Inordinate compile times on large routines In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "steven 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-12/txt/msg01858.txt.bz2 ------- Comment #39 from steven at gcc dot gnu dot org 2007-12-20 00:02 ------- We badly need a way to track memory in DF. Because DF uses alloc_pools for almost all its data structures, the memory statistics are only recorded if you configure with --gather-detailed-mem-stats. I think it would be good if the DF problems would report an estimate of their memory usage in the dump files, or if a function would be available that you can call from GDB to give such an estimate. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854