[Bug rtl-optimization/39077] [4.3/4.4/4.5/4.6 Regression] GCSE-optimization causes enormous binary size increase (~20 times !)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39077 Robert Hinson oppiet35 at yahoo dot com changed: What|Removed |Added CC||oppiet35 at yahoo dot com --- Comment #23 from Robert Hinson oppiet35 at yahoo dot com 2011-11-25 13:08:08 UTC --- I know this is an old bug. Probably been fixed since then. I am using: [oppie@fedora ~]$ g++ -v Using built-in specs. COLLECT_GCC=/usr/bin/g++ COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-redhat-linux/4.6.2/lto-wrapper Target: i686-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch=i686 --build=i686-redhat-linux Thread model: posix gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) This is on a fedora core 16 box. :) without the -fno-gcse switch I get a file with this size: -rw-rw-r--. 1 oppie oppie 647512 Nov 25 06:49 SSMprotocol_def_en.o With the --fno-gcse switch I get a file with this size: -rw-rw-r--. 1 oppie oppie 649136 Nov 25 07:00 SSMprotocol_def_en.o I also get an error: src/SSMprotocol_def_en.cpp: In constructor ‘SSMprotocol_def_en::SSMprotocol_def_en()’: src/SSMprotocol_def_en.cpp:23:2: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without :)
[Bug rtl-optimization/39077] [4.3/4.4/4.5/4.6 Regression] GCSE-optimization causes enormous binary size increase (~20 times !)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39077 --- Comment #21 from Jeffrey A. Law law at gcc dot gnu.org 2011-01-13 13:41:09 UTC --- Author: law Date: Thu Jan 13 13:41:03 2011 New Revision: 168747 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=168747 Log: * PR rtl-optimization/39077 * doc/invoke.texi (max-gcse-insertion-ratio): Document. * params.h (MAX_GCSE_INSERTION_RATIO): Define. * params.def (PARAM_MAX_GCSE_INSERTION_RATIO): Define. * lcm.c (pre_edge_lcm): Properly initialize output sbitmaps. * gcse.c (prune_insertions_deletions): New function. (compute_pre_data): Use it. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/invoke.texi trunk/gcc/gcse.c trunk/gcc/lcm.c trunk/gcc/params.def trunk/gcc/params.h
[Bug rtl-optimization/39077] [4.3/4.4/4.5/4.6 Regression] GCSE-optimization causes enormous binary size increase (~20 times !)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39077 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Target Milestone|4.3.6 |4.6.0 --- Comment #22 from Jeffrey A. Law law at redhat dot com 2011-01-13 13:42:16 UTC --- Fixed on trunk
[Bug rtl-optimization/39077] [4.3/4.4/4.5/4.6 Regression] GCSE-optimization causes enormous binary size increase (~20 times !)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39077 --- Comment #20 from Jeffrey A. Law law at redhat dot com 2011-01-13 04:12:10 UTC --- http://gcc.gnu.org/ml/gcc-patches/2011-01/msg00797.html Apparently I didn't format my subject line correctly...
[Bug rtl-optimization/39077] [4.3/4.4/4.5/4.6 Regression] GCSE-optimization causes enormous binary size increase (~20 times !)
--- Comment #19 from rguenth at gcc dot gnu dot org 2010-05-22 18:13 --- 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=39077
[Bug rtl-optimization/39077] [4.3/4.4/4.5/4.6 Regression] GCSE-optimization causes enormous binary size increase (~20 times !)
--- Comment #18 from comer352l at googlemail dot com 2010-04-09 15:35 --- (In reply to comment #17) In the meantime I managed to test on a windows machine with a recent version (4.4.0) and the size increase doesn't occur there (but compilation is extremely slow, too). Sorry, it seems I've made a mistake during my last test: the size increasing occurs on Windows, too. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39077
