From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30680 invoked by alias); 29 Aug 2006 10:36:17 -0000 Received: (qmail 30650 invoked by uid 48); 29 Aug 2006 10:36:10 -0000 Date: Tue, 29 Aug 2006 10:36:00 -0000 Message-ID: <20060829103610.30649.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/28871] massive C++ compile time slowdown In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "bkoz at gcc dot gnu dot org" 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 X-SW-Source: 2006-08/txt/msg02530.txt.bz2 List-Id: ------- Comment #2 from bkoz at gcc dot gnu dot org 2006-08-29 10:36 ------- More info. I was able to take mainline libstdc++ sources, modify limits, --disable-visibility and then run check-compile on the same machine/os/sources with both 4_1-branch and mainline (20060827). The time just to compile the libstdc++ testsuite is: gcc-4_1-branch --disable-visibility 1626.889u 142.268s 34:30.18 85.4% 0+0k 0+0io 0pf+0w gcc --disable-visibility 1713.939u 152.437s 32:24.81 95.9% 0+0k 0+0io 4pf+0w gcc 1885.657u 126.063s 34:21.40 97.5% 0+0k 0+0io 0pf+0w This is compiling with a PCH (which appears to be used from -Winvalid-pch and -H), but no linking or executing. Still seems slower than I remember it being a month ago, but I'll try to isolate more, and then come up with something simple that can be used to fix this. It does not look like the visibilty support impacts compile time. That's good. These times are close enough to be a wash. So, I think we can remove the C++FE from the list of slowdown candidates. (Which includes libstdc++, g++, optmizers.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28871