This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/36291] [4.3/4.4 Regression] GCC is slow and memory-hungry building sipQtGuipart.cpp
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Jun 2008 20:26:19 -0000
- Subject: [Bug tree-optimization/36291] [4.3/4.4 Regression] GCC is slow and memory-hungry building sipQtGuipart.cpp
- References: <bug-36291-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #13 from rguenth at gcc dot gnu dot org 2008-06-06 20:26 -------
Fixed. The remaining slowness is a dup of PR33237.
Memory usage on the branch is now down to ~700MB peak VM usage on a 3GB machine
at -O on x86_64. Compile time is down to
tree find ref. vars : 12.26 (10%) usr 0.27 ( 4%) sys 12.44 (10%) wall
199898 kB (18%) ggc
tree alias analysis : 5.04 ( 4%) usr 0.10 ( 2%) sys 5.15 ( 4%) wall
1716 kB ( 0%) ggc
tree call clobbering : 12.50 (10%) usr 0.05 ( 1%) sys 12.54 (10%) wall
592 kB ( 0%) ggc
tree memory partitioning: 32.74 (26%) usr 0.23 ( 4%) sys 32.94 (25%) wall
880 kB ( 0%) ggc
tree SSA incremental : 3.29 ( 3%) usr 0.04 ( 1%) sys 3.25 ( 3%) wall
3714 kB ( 0%) ggc
tree operand scan : 8.62 ( 7%) usr 0.17 ( 3%) sys 8.59 ( 7%) wall
59455 kB ( 5%) ggc
TOTAL : 121.52 6.89 128.51
1141231 kB
of course 4.1 took 34s and only 600MB.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Known to fail| |4.3.1
Known to work| |4.1.3
Resolution| |FIXED
Summary|GCC is slow and memory- |[4.3/4.4 Regression] GCC is
|hungry building |slow and memory-hungry
|sipQtGuipart.cpp |building sipQtGuipart.cpp
Target Milestone|--- |4.3.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36291