[Bug tree-optimization/58318] very slow compilation on x86_64-linux with -O3 and -g and checking enabled

[asolokha at gmx dot com]

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

Arseny Solokha  changed:

   What|Removed |Added

 CC||asolokha at gmx dot com

--- Comment #4 from Arseny Solokha  ---
I cannot reproduce it on all active branches. It looks like 4.8 was the last
branch w/ this issue.

[Bug tree-optimization/58318] very slow compilation on x86_64-linux with -O3 and -g and checking enabled

[su at cs dot ucdavis.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58318

--- Comment #3 from Zhendong Su su at cs dot ucdavis.edu ---
 A quick check with a non-bootstrapped cc1 but release checking makes the
 slowdown go away.

Richard, there is related testcase that I have just reported (58479). It
manifests also under release checking. Thanks.

[Bug tree-optimization/58318] very slow compilation on x86_64-linux with -O3 and -g and checking enabled

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58318

Richard Biener rguenth at gcc dot gnu.org changed:

   What|Removed |Added

   Keywords||compile-time-hog
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2013-09-05
Version|unknown |4.9.0
Summary|very slow compilation on|very slow compilation on
   |x86_64-linux with -O3 and   |x86_64-linux with -O3 and
   |-g  |-g and checking enabled
 Ever confirmed|0   |1

--- Comment #1 from Richard Biener rguenth at gcc dot gnu.org ---
Confirmed.  We completely unroll the loop nest in bar () after inlining foo ().
In the -g case we retain a ton of DEBUG_STMTs - 577185 - in a single basic
block.  So walking all of them causes the slowdown, the walking done by
the verifiers - did you compare trunk with --enable-checking=release?  I can
see the same stmts with using GCC 4.8.

A quick check with a non-bootstrapped cc1 but release checking makes the
slowdown go away.

Still, eventually the checkers may need some speed related TLC.

[Bug tree-optimization/58318] very slow compilation on x86_64-linux with -O3 and -g and checking enabled

[su at cs dot ucdavis.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58318

--- Comment #2 from Zhendong Su su at cs dot ucdavis.edu ---
 did you compare trunk with --enable-checking=release?  

Richard, you are right. Below is my 4.8 config: 

$ gcc-4.8 -v
Using built-in specs.
COLLECT_GCC=gcc-4.8
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.8/libexec/gcc/x86_64-unknown-linux-gnu/4.8.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.8.1/configure
--enable-languages=c,c++,objc,obj-c++,fortran,lto --disable-checking
--with-gmp=/usr/local/gcc-4.8 --with-mpfr=/usr/local/gcc-4.8
--with-mpc=/usr/local/gcc-4.8 --with-cloog=/usr/local/gcc-4.8
--prefix=/usr/local/gcc-4.8
Thread model: posix
gcc version 4.8.1 (GCC) 
$