From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16056 invoked by alias); 19 May 2003 20:43:21 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14881 invoked from network); 19 May 2003 20:43:04 -0000 Received: from unknown (HELO mailout09.sul.t-online.com) (194.25.134.84) by sources.redhat.com with SMTP; 19 May 2003 20:43:04 -0000 Received: from fwd03.sul.t-online.de by mailout09.sul.t-online.com with smtp id 19HrT3-0003El-09; Mon, 19 May 2003 22:42:45 +0200 Received: from kolme (520028553724-0001@[80.138.160.53]) by fmrl03.sul.t-online.com with esmtp id 19HrSw-2DzFbcC; Mon, 19 May 2003 22:42:38 +0200 Received: from goofy.hamnixda.de ([192.168.100.249] helo=goofy) by kolme with esmtp (Exim 3.35 #1 (Debian)) id 19HrSu-0000Z0-00; Mon, 19 May 2003 22:42:36 +0200 Received: from richard (helo=localhost) by goofy with local-esmtp (Exim 3.36 #1 (Debian)) id 19HrSu-0004bD-00; Mon, 19 May 2003 22:42:36 +0200 Date: Mon, 19 May 2003 20:51:00 -0000 From: Richard Guenther To: Matt Austern cc: gcc@gcc.gnu.org Subject: Re: Huge compile time & run time performance regression 3.3 -> HEAD In-Reply-To: <110B848B-8A12-11D7-B0E8-000393B2ABA2@apple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 520028553724-0001@t-dialin.net X-SW-Source: 2003-05/txt/msg01795.txt.bz2 On Mon, 19 May 2003, Matt Austern wrote: > On Sunday, May 18, 2003, at 08:45 AM, Richard Guenther wrote: > > > Hi! > > > > As 3.3 is now out, I start comparing 3.3 to HEAD wrt compile time > > performance and performance of the resulting code. As always these > > comparisons are for a POOMA based scientific application. > > > > I experience a 100% compile time regression (673.50s -> 1284.48s) and > > a 12% runtime performance regression (150s -> 171s) when comparing > > gcc3.3 to HEAD. > > > > Time reports follow, the most prominent regressions are expand, global > > CSE > > (>300%!), loop analysis and branch prediction. > > > > Compile options are -ftemplate-depth-80 -fno-exceptions -O2 > > -march=athlon > > -funroll-loops -fomit-frame-pointer > > Do you see any compile time regressions at -O0? > > (I'm asking for the obvious reason: trying to find out how much work we > need to do in the front end as opposed to the back end.) After killing all forced inlining, I get almost the same timings from 3.3 and 3.4, namely 42.50 and 44.89 seconds. Slowdown comes from 3.3: name lookup : 6.92 (17%) usr 0.90 (43%) sys 7.50 (18%) wall 3.4: name lookup : 9.06 (22%) usr 0.81 (39%) sys 10.29 (23%) wall Richard.