From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21684 invoked by alias); 17 Feb 2010 16:57:02 -0000 Received: (qmail 21629 invoked by uid 48); 17 Feb 2010 16:56:50 -0000 Date: Wed, 17 Feb 2010 16:57:00 -0000 Message-ID: <20100217165650.21628.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug rtl-optimization/43058] [4.5 Regression] var-tracking uses up all virtual memory In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mmitchel 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: 2010-02/txt/msg01671.txt.bz2 ------- Comment #7 from mmitchel at gcc dot gnu dot org 2010-02-17 16:56 ------- I think this is a critical problem. If var-tracking is causing factor-of-N increases in memory usage, then we need an algorithmic change that prevents that, even if that means inferior debug information. We're not going to win friends and influence people by giving them a compiler that can't compile things on their system, or takes much longer to do it, even if their debugging experience is better. -- mmitchel at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43058