From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27453 invoked by alias); 21 Aug 2010 14:36:32 -0000 Received: (qmail 27397 invoked by uid 48); 21 Aug 2010 14:36:14 -0000 Date: Sat, 21 Aug 2010 14:36:00 -0000 Message-ID: <20100821143614.27396.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mikpe at it dot uu dot se" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-08/txt/msg01742.txt.bz2 ------- Comment #4 from mikpe at it dot uu dot se 2010-08-21 14:36 ------- Well something in -g processing is a CPU hog. On my Turion X2 Ultra ZM-82 laptop (2.2GHz x 2 cores) with 32-bit kernel and vanilla gcc-4.5.1 (--enable-checking=release) I get: > time gcc -m32 -O0 -c pr45364.i 1.220u 0.120s 0:01.35 99.2% 0+0k 0+0io 0pf+0w > time gcc -m32 -O0 -g -c pr45364.i 1.500u 0.060s 0:01.57 99.3% 0+0k 0+0io 0pf+0w > time gcc -m32 -O1 -c pr45364.i 3.100u 0.100s 0:03.21 99.6% 0+0k 0+0io 0pf+0w > time gcc -m32 -O1 -g -c pr45364.i 22.590u 0.190s 0:22.81 99.8% 0+0k 0+0io 0pf+0w > time gcc -m32 -O2 -c pr45364.i 8.680u 0.210s 0:08.93 99.5% 0+0k 0+0io 0pf+0w > time gcc -m32 -O2 -g -c pr45364.i 238.490u 0.340s 3:58.97 99.9% 0+0k 0+0io 0pf+0w During the last -O2 -g run I ran top and cc1 only used about 200MB, so swapping is not the problem. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45364