[Bug tree-optimization/26854] Inordinate compile times on large routines

["lucier at math dot purdue.edu" <gcc-bugzilla at gcc dot gnu dot org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854

--- Comment #131 from lucier at math dot purdue.edu ---
Created attachment 37761
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37761&action=edit
time/memory report compiling _num.i with -O2

This bug, perhaps related,

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37448

was just closed, so I thought I would try to compile all.i, compiler.i, and
_num.i with today's mainline

heine:~/Downloads> /pkgs/gcc-mainline/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/pkgs/gcc-mainline/bin/gcc
COLLECT_LTO_WRAPPER=/pkgs/gcc-mainline/libexec/gcc/x86_64-pc-linux-gnu/6.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../../gcc-mainline/configure --prefix=/pkgs/gcc-mainline
--enable-checking=release --enable-languages=c --disable-multilib
Thread model: posix
gcc version 6.0.0 20160222 (experimental) (GCC) 

with the options:

/pkgs/gcc-mainline/bin/gcc -v -c -O2 -fmem-report -ftime-report all.i
-save-temps > & ! report-compiler-all

I had to kill the compiles of all.i and compiler.i when memory usage got up to
32GB.

This file is the time and memory report from compiling _num.i.