From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2456 invoked by alias); 28 Oct 2002 21:40:41 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2431 invoked by uid 61); 28 Oct 2002 21:40:41 -0000 Date: Mon, 28 Oct 2002 13:40:00 -0000 Message-ID: <20021028214040.2430.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tsv@solvo.ru From: bangerth@dealii.org Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tsv@solvo.ru, gcc-gnats@gcc.gnu.org Subject: Re: c++/7441: large compilation time regression with string array initialization X-SW-Source: 2002-10/txt/msg01179.txt.bz2 List-Id: Old Synopsis: compilation by g++ take long time New Synopsis: large compilation time regression with string array initialization State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Mon Oct 28 13:40:39 2002 State-Changed-Why: I can confirm this. Compile times go through the roof from 1.5 sec (gcc 2.95) to about 3 minutes (3.2.1 and CVS). The underlying problem is initialization of an insanely large array of string constants. This is a C++ front end problem, since if the file is compiled with the C front end, compile times are negligible. Note that for the problem, one needs not even specify optimization flags. Thus, there is no way to avoid it... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7441