Testcase is from PR30052:
http://gcc.gnu.org/bugzilla/attachment.cgi?id=13678
current GCC 4.3 branch gives us a peak memory usage of 1.8GB on x86_64 and
tree find ref. vars : 15.36 ( 5%) usr 0.80 ( 8%) sys 15.90 ( 5%) wall
817801 kB (35%) ggc
tree alias analysis : 16.27 ( 5%) usr 0.38 ( 4%) sys 16.11 ( 5%) wall
11037 kB ( 0%) ggc
tree call clobbering : 41.35 (14%) usr 0.28 ( 3%) sys 43.00 (14%) wall
3132 kB ( 0%) ggc
tree flow insensitive alias: 31.26 (10%) usr 0.34 ( 3%) sys 31.94 (10%)
wall 0 kB ( 0%) ggc
tree memory partitioning: 83.32 (28%) usr 0.89 ( 9%) sys 84.36 (27%) wall
974 kB ( 0%) ggc
tree SSA incremental : 10.60 ( 4%) usr 0.17 ( 2%) sys 11.11 ( 4%) wall
15755 kB ( 1%) ggc
tree operand scan : 28.71 (10%) usr 0.57 ( 6%) sys 29.59 ( 9%) wall
160271 kB ( 7%) ggc
TOTAL : 301.74 9.75 314.50
2354835 kB
--
Summary: GCC is slow and memory-hungry building sipQtGuipart.cpp
Product: gcc
Version: 4.3.1
Status: UNCONFIRMED
Keywords: memory-hog, compile-time-hog
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rguenth at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36291
