[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |compile-time-hog
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-02-02
               Host|i686-pc-linux-gnu           |
     Ever Confirmed|0                           |1
              Build|i686-pc-linux-gnu           |
           Severity|enhancement                 |minor

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-02 17:35:42 UTC ---
With checking still enabled we get:
-O1 -g:
 var-tracking dataflow   :   7.73 (57%) usr   0.05 (12%) sys   7.78 (56%) wall 
     0 kB ( 0%) ggc
-O2 -g:
 var-tracking dataflow   :  15.23 (45%) usr   0.07 (13%) sys  15.33 (45%) wall 
     0 kB ( 0%) ggc

-O2:
 CPROP                   :   4.35 (27%) usr   0.02 ( 4%) sys   4.36 (27%) wall 
  2486 kB ( 3%) ggc


on the trunk.
I have not checked without checking enabled.

So confirmed but it has improved a lot already.

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[rguenth at gcc dot gnu.org]

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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 28 09:02:59 2014
New Revision: 207172

URL: http://gcc.gnu.org/viewcvs?rev=207172&root=gcc&view=rev
Log:
2014-01-28  Richard Biener  <rguenther@suse.de>

    PR rtl-optimization/45364
    PR rtl-optimization/59890
    * var-tracking.c (local_get_addr_clear_given_value): Handle
    already cleared slot.
    (val_reset): Handle not allocated local_get_addr_cache.
    (vt_find_locations): Use post-order on the inverted CFG.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/var-tracking.c

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[rguenth at gcc dot gnu.org]

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

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 28 13:13:54 2014
New Revision: 207182

URL: http://gcc.gnu.org/viewcvs?rev=207182&root=gcc&view=rev
Log:
2014-01-28  Richard Biener  <rguenther@suse.de>

    Revert
    2014-01-28  Richard Biener  <rguenther@suse.de>

    PR rtl-optimization/45364
    PR rtl-optimization/59890
    * var-tracking.c (local_get_addr_clear_given_value): Handle
    already cleared slot.
    (val_reset): Handle not allocated local_get_addr_cache.
    (vt_find_locations): Use post-order on the inverted CFG.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/var-tracking.c

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[jakub at gcc dot gnu dot org]

------- Comment #6 from jakub at gcc dot gnu dot org  2010-08-21 15:56 -------
On the trunk this takes (--enable-checking=release)

time ./cc1 -g -O2 -quiet directx.i

real    2m49.038s
user    2m48.489s
sys     0m0.268s

here.  As InitAdapters is quite large, with more than thousand calls in it,
this isn't very surprising.


-- 


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

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[mikpe at it dot uu dot se]

------- Comment #5 from mikpe at it dot uu dot se  2010-08-21 15:44 -------
(In reply to comment #4)
> Well something in -g processing is a CPU hog.  On my Turion X2 Ultra ZM-82
> laptop (2.2GHz x 2 cores) with 32-bit kernel and vanilla gcc-4.5.1
> (--enable-checking=release) I get:

Same machine, but running a 64-bit kernel and using a 64-bit gcc-4.5.1:

> time gcc -m32 -O0 -c pr45364.i
1.390u 0.090s 0:01.49 99.3%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O0 -g -c pr45364.i
1.630u 0.060s 0:01.71 98.8%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O1 -c pr45364.i
3.690u 0.090s 0:03.80 99.4%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O1 -g -c pr45364.i
26.740u 0.230s 0:27.00 99.8%    0+0k 0+0io 0pf+0w
> time gcc -m32 -O2 -c pr45364.i
10.960u 0.220s 0:11.52 97.0%    0+0k 0+0io 0pf+0w
> time gcc -m32 -O2 -g -c pr45364.i
291.430u 0.540s 4:52.15 99.9%   0+0k 0+0io 0pf+0w

In the last -O2 -g run cc1 used about 344MB of address space.

So it doesn't take forever but -g is definitely a CPU hog.


-- 


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

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[mikpe at it dot uu dot se]

------- Comment #4 from mikpe at it dot uu dot se  2010-08-21 14:36 -------
Well something in -g processing is a CPU hog.  On my Turion X2 Ultra ZM-82
laptop (2.2GHz x 2 cores) with 32-bit kernel and vanilla gcc-4.5.1
(--enable-checking=release) I get:

> time gcc -m32 -O0  -c pr45364.i
1.220u 0.120s 0:01.35 99.2%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O0 -g -c pr45364.i
1.500u 0.060s 0:01.57 99.3%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O1 -c pr45364.i
3.100u 0.100s 0:03.21 99.6%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O1 -g -c pr45364.i
22.590u 0.190s 0:22.81 99.8%    0+0k 0+0io 0pf+0w
> time gcc -m32 -O2 -c pr45364.i
8.680u 0.210s 0:08.93 99.5%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O2 -g -c pr45364.i
238.490u 0.340s 3:58.97 99.9%   0+0k 0+0io 0pf+0w

During the last -O2 -g run I ran top and cc1 only used about 200MB, so swapping
is not the problem.


-- 


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

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[hjl dot tools at gmail dot com]

------- Comment #3 from hjl dot tools at gmail dot com  2010-08-21 05:13 -------
On Linux/Intel64, I got

time /usr/gcc-4.5/bin/gcc -m32 -O2  pr45364.i -g -c      /tmp
/usr/gcc-4.5/bin/gcc -m32 -O2 pr45364.i -g -c  110.63s user 0.17s system 99%
cpu 1:50.87 total
[hjl@gnu-6 tmp]$ /usr/gcc-4.5/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/usr/gcc-4.5/bin/gcc
COLLECT_LTO_WRAPPER=/usr/gcc-4.5/libexec/gcc/x86_64-unknown-linux-gnu/4.5.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /net/gnu-13/export/gnu/src/gcc-4.5/gcc/configure
--enable-clocale=gnu --with-system-zlib --enable-checking=assert
--with-demangler-in-ld --enable-shared --enable-threads=posix --enable-haifa
--prefix=/usr/gcc-4.5 --with-local-prefix=/usr/local --with-plugin-ld=ld.gold
--enable-gold --with-fpmath=sse
Thread model: posix
gcc version 4.5.1 (GCC) 
[hjl@gnu-6 tmp]$ 


-- 


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

[Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time

[bero at arklinux dot org]

------- Comment #2 from bero at arklinux dot org  2010-08-21 01:10 -------
Assumed it was an infinite loop a bit too early -- it did finish after giving
it some more time.

There is a speed problem though. Updating summary and severity.


-- 

bero at arklinux dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
            Summary|Apparent infinite loop while|Compiling wine's directx.c
                   |compiling wine's directx.c  |with -O1 -g takes a very
                   |with -O1 -g                 |long time


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