------- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-25
04:28 -------
branch prediction : 4.63 (17%) usr 0.78 (16%) sys 5.57 (16%) wall
187672 kB (61%) ggc
Memory usage here is a big problem.
fold-const.c:2981 (invert_truthvalue) 36146592:15.8% 0:
0.0% 0: 0.0% 0:
0.0% 1004072
fold-const.c:10456 (fold_build2) 90093096:39.5% 0:
0.0% 0: 0.0% 0: 0.0%
2502586
tree-ssa-dom.c:1435 (build_and_record_new_cond) 685080: 0.3% 0:
0.0% 0: 0.0%
0: 0.0% 19030
tree-ssa-propagate.c:246 (add_ssa_edge) 0: 0.0% 89488:
0.3% 0: 0.0% 24464:
0.3% 28
tree-ssa-propagate.c:248 (add_ssa_edge) 0: 0.0%
5820032:22.3% 0: 0.0%
1577088:17.3% 36
Hmm, why is varying_ssa_edges in GC memory? Likewise for interesting_ssa_edges?
Unless someone wants tree-ssa-propagate.c to be able to call ggc_collect while
propagating.
--
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |memory-hog
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18594
