------- Additional Comments From steven at gcc dot gnu dot org 2005-01-21
14:00 -------
For the test case from comment #1 I get the following for AMD64:
GCC 4.0 (20050121):
text data bss dec hex filename
24689 0 0 24689 6071 t.O2.o
20728 0 0 20728 50f8 t.Os.o
GCC 3.3-SUSE (pre 3.3.5 20040809 hammer-branch)
22682 0 0 22682 589a t.O2.o
21281 0 0 21281 5321 t.Os.o
and for i686:
GCC 4.0 (20050121):
24064 0 0 24064 5e00 t.O2.o
19479 0 0 19479 4c17 t.Os.o
GCC 3.3-SUSE (pre 3.3.5 20040809 hammer-branch) -m32
19646 0 0 19646 4cbe t.O2.o
17713 0 0 17713 4531 t.Os.o
So I am seeing a 10% code size increase at -O2 for GCC 4.0 compared to the
hammer-branch based GCC 3.3. GCC 3.3 was the best score we had for this so
far. The 35% from the subject is quite exaggerated, so I have adjusted it.
(FWIW, the GCC 4.0 I tested has my patch for PR19454 applied, which makes
quite a difference for -m32 -O2, but not for -Os...).
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.0 Regression] 35% |[4.0 Regression] 10%
|increase in codesize with C |increase in codesize with C
|code |code compared to GCC 3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17549
