From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27612 invoked by alias); 16 Dec 2004 10:30:40 -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 27515 invoked by uid 48); 16 Dec 2004 10:30:34 -0000 Date: Thu, 16 Dec 2004 10:30:00 -0000 Message-ID: <20041216103034.27514.qmail@sourceware.org> From: "david at starks-browning dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041215190517.19018.david@starks-browning.com> References: <20041215190517.19018.david@starks-browning.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/19018] [3.3 Regression] virtual memory exhausted X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg02344.txt.bz2 List-Id: ------- Additional Comments From david at starks-browning dot com 2004-12-16 10:30 ------- True, but I don't believe the patch for PR16273 is applicable to gcc-3.3. In fact, I am unable to reproduce the fault in gcc-3.3 using the 10,000-line test case that was attached to PR16273. Therefore, my guess is that the smaller test case (attachment id 6664) was refined against gcc-3.4 and led to the patch that fixed the symptom in gcc-3.4. I don't know how much of that effort could be applied to gcc-3.3. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19018