[Bug tree-optimization/18219] [4.3/4.4 Regression] bloats code by 31%
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18219 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Target Milestone|4.3.6 |4.4.7 --- Comment #33 from Richard Guenther rguenth at gcc dot gnu.org 2011-06-27 12:12:39 UTC --- 4.3 branch is being closed, moving to 4.4.7 target.
[Bug tree-optimization/18219] [4.3/4.4 Regression] bloats code by 31%
--- Comment #32 from rguenth at gcc dot gnu dot org 2010-05-22 18:10 --- GCC 4.3.5 is being released, adjusting target milestone. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.3.5 |4.3.6 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18219
[Bug tree-optimization/18219] [4.3/4.4 Regression] bloats code by 31%
--- Comment #30 from steven at gcc dot gnu dot org 2010-01-03 22:57 --- With the following compiler: $ ./xgcc --version xgcc (GCC) 4.5.0 20091228 (experimental) [trunk revision 155486] Copyright (C) 2009 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I get the following size with -m32 for the test case of comment #0: $ ./xgcc -B. -c t.c -m32 -Os -fno-ivopts -o tOsi.o $ ./xgcc -B. -c t.c -m32 -Os -o tOs.o $ size tOs* textdata bss dec hex filename 45 0 0 45 2d tOsi.o 42 0 0 42 2a tOs.o $ And I get the following size with -m64: $ ./xgcc -B. -c t.c -Os -o tOs.o $ ./xgcc -B. -c t.c -Os -fno-ivopts -o tOsi.o $ size tOs* textdata bss dec hex filename 78 0 0 78 4e tOsi.o 89 0 0 89 59 tOs.o $ This is, therefore, fixed on the trunk for GCC 4.5. -- steven at gcc dot gnu dot org changed: What|Removed |Added Known to work||4.5.0 Summary|[4.3/4.4/4.5 Regression]|[4.3/4.4 Regression] bloats |bloats code by 31% |code by 31% http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18219
[Bug tree-optimization/18219] [4.3/4.4 Regression] bloats code by 31%
--- Comment #31 from rguenth at gcc dot gnu dot org 2010-01-03 23:14 --- Heh. I wonder how we can reliably add testcases for code size issues ... can we either dump size estimates or extract object .text section sizes? Ian may know arm people who I suspect would be interested in contributing infrastructure for this. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added CC||iant at google dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18219