From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7462 invoked by alias); 9 Feb 2005 08:14:47 -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 7122 invoked by uid 48); 9 Feb 2005 08:14:07 -0000 Date: Wed, 09 Feb 2005 14:05:00 -0000 Message-ID: <20050209081407.7121.qmail@sourceware.org> From: "mmitchel at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041002222357.17798.rth@gcc.gnu.org> References: <20041002222357.17798.rth@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug preprocessor/17798] [3.4/4.0 Regression] high cpp memory usage with undefined symbols X-Bugzilla-Reason: CC X-SW-Source: 2005-02/txt/msg00637.txt.bz2 List-Id: ------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-02-09 08:13 ------- This is nowhere near release-critical; it's an intentional extreme corner case. As for the facts noted in the audit trail (i.e., that we lex the whole file up front, and that we keep all identifiers around the entire time), those are very sound strategies for most programs. I've removed the target milestone, and closed as WONTFIX. If someone chooses to reopen this, please do not reset the target milestone. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX Target Milestone|3.4.4 |--- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17798