------- Comment #5 from mikpe at it dot uu dot se 2010-08-21 15:44 ------- (In reply to comment #4) > 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:
Same machine, but running a 64-bit kernel and using a 64-bit gcc-4.5.1: > time gcc -m32 -O0 -c pr45364.i 1.390u 0.090s 0:01.49 99.3% 0+0k 0+0io 0pf+0w > time gcc -m32 -O0 -g -c pr45364.i 1.630u 0.060s 0:01.71 98.8% 0+0k 0+0io 0pf+0w > time gcc -m32 -O1 -c pr45364.i 3.690u 0.090s 0:03.80 99.4% 0+0k 0+0io 0pf+0w > time gcc -m32 -O1 -g -c pr45364.i 26.740u 0.230s 0:27.00 99.8% 0+0k 0+0io 0pf+0w > time gcc -m32 -O2 -c pr45364.i 10.960u 0.220s 0:11.52 97.0% 0+0k 0+0io 0pf+0w > time gcc -m32 -O2 -g -c pr45364.i 291.430u 0.540s 4:52.15 99.9% 0+0k 0+0io 0pf+0w In the last -O2 -g run cc1 used about 344MB of address space. So it doesn't take forever but -g is definitely a CPU hog. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45364
