------- 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
