------- Comment #31 from rguenth at gcc dot gnu dot org 2010-06-24 08:42
-------
Surely not.
> g++-4.5 -S -o /dev/null MRApStyle.cc -O2 -g -ftime-report
MRApStyle.cc: In constructor MRApStyle::MRApStyle():
MRApStyle.cc:2409:1: note: variable tracking size limit exceeded with
-fvar-tracking-assignments, retrying without
variable tracking : 88.42 (55%) usr 0.52 (20%) sys 89.28 (54%) wall
82333 kB (14%) ggc
TOTAL : 161.23 2.64 164.58
579368 kB
on the top of the 4.5 branch. Everything else looks good now, so we can
as well claim its one of the dups of the var-tracking-is-slow-and-memory-hungry
bugs.
90s var-tracking and then giving up is quite bad. Can't we estimate instead
of compute and give up?
4.4 needed 186s even without the var-tracking slowness, so at least we
have recovered for that elsewhere... (in operand-scan, aka alias-improvements)
Biggest offenders in 4.5 without -g are
df live regs : 4.66 ( 7%) usr 0.04 ( 2%) sys 4.77 ( 7%) wall
0 kB ( 0%) ggc
df live&initialized regs: 3.17 ( 5%) usr 0.03 ( 1%) sys 3.28 ( 5%) wall
0 kB ( 0%) ggc
expand : 4.51 ( 7%) usr 0.11 ( 5%) sys 4.56 ( 7%) wall
45724 kB (14%) ggc
CPROP : 2.36 ( 4%) usr 0.08 ( 4%) sys 2.43 ( 4%) wall
10379 kB ( 3%) ggc
PRE : 3.80 ( 6%) usr 0.18 ( 9%) sys 4.03 ( 6%) wall
9490 kB ( 3%) ggc
integrated RA : 5.56 ( 8%) usr 0.06 ( 3%) sys 5.64 ( 8%) wall
3140 kB ( 1%) ggc
reload : 2.79 ( 4%) usr 0.08 ( 4%) sys 2.93 ( 4%) wall
14680 kB ( 4%) ggc
reload CSE regs : 6.40 (10%) usr 0.09 ( 4%) sys 6.53 (10%) wall
13311 kB ( 4%) ggc
scheduling 2 : 2.64 ( 4%) usr 0.05 ( 2%) sys 2.69 ( 4%) wall
278 kB ( 0%) ggc
TOTAL : 65.64 2.01 68.05
338657 kB
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12392
