[Bug target/40735] [4.3/4.4/4.5/4.6/4.7 Regression] memory hog compiling big functions with -fPIE

[Bug target/40735] [4.3/4.4/4.5/4.6/4.7 Regression] memory hog compiling big functions with -fPIE

[rguenth at gcc dot gnu.org]

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.3.6                       |4.4.7

--- Comment #13 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-06-27 12:14:51 UTC ---
4.3 branch is being closed, moving to 4.4.7 target.

[Bug target/40735] [4.4/4.5/4.6/4.7 Regression] memory hog compiling big functions with -fPIE

[rguenth at gcc dot gnu.org]

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |4.6.2, 4.7.0

--- Comment #14 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-16 14:16:09 UTC ---
(In reply to comment #4)
> This is likely caused by the DF merge.  There are numerous bugs about this
> already and nothing really can be done here.
> 
> Btw, my numbers are
> 
> rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 744108 kB
> rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.3 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 719836 kB
> rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.2 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 459757 kB

> ~/bin/maxmem2.sh gcc-4.6 -S -o /dev/null t.i -v -std=gnu99 -Os -fPIE -fstack-protector -g
total: 772239 kB
> ~/bin/maxmem2.sh gcc-4.7 -S -o /dev/null t.i -v -std=gnu99 -Os -fPIE -fstack-protector -g --param ggc-min-expand=100 --param ggc-min-heapsize=131072
total: 794883 kB

we're continuing to increase, thus re-confirmed.

[Bug target/40735] memory hog compiling big functions with -fPIE

[rguenth at gcc dot gnu.org]

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |47344
   Target Milestone|4.4.7                       |---
            Summary|[4.4/4.5/4.6/4.7            |memory hog compiling big
                   |Regression]  memory hog     |functions with -fPIE
                   |compiling big functions     |
                   |with -fPIE                  |

--- Comment #15 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-16 14:29:20 UTC ---
Blocks the memory-hog meta-bug which is marked as regression.

[Bug target/40735] memory hog compiling big functions with -fPIE

[xiaoyuanbo at yeah dot net]

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

xiaoyuanbo <xiaoyuanbo at yeah dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xiaoyuanbo at yeah dot net

--- Comment #16 from xiaoyuanbo <xiaoyuanbo at yeah dot net> 2012-02-22 12:52:59 UTC ---
obtain head

[Bug target/40735] memory hog compiling big functions with -fPIE

[steven at gcc dot gnu.org]

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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |steven at gcc dot gnu.org
         AssignedTo|unassigned at gcc dot       |steven at gcc dot gnu.org
                   |gnu.org                     |

[Bug target/40735] memory hog compiling big functions with -fPIE

[steven at gcc dot gnu.org]

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

--- Comment #17 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-28 08:43:58 UTC ---
(In reply to comment #4)
> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 744108 kB

richi, can you share this maxmem2 script?

[Bug target/40735] memory hog compiling big functions with -fPIE

[amonakov at gcc dot gnu.org]

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

--- Comment #18 from Alexander Monakov <amonakov at gcc dot gnu.org> 2012-08-28 08:48:28 UTC ---
(In reply to comment #17)
> 
> richi, can you share this maxmem2 script?

It's available on the wiki: http://gcc.gnu.org/wiki/PerformanceTesting

[Bug target/40735] memory hog compiling big functions with -fPIE

[steven at gcc dot gnu.org]

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

--- Comment #19 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-28 09:34:10 UTC ---
With r190665, compile time is mostly spent in:
 loop doloop             : 130.15 ( 8%) usr
 variable tracking       : 990.72 (60%) usr
 var-tracking dataflow   :  76.34 ( 5%) usr

So this isn't a DF issue in GCC 4.8 at least, but yet another var-tracking
issue (but probably not related to bug 53958, because var-tracking dataflow
time is almost reasonable here).

I'll have a look at the doloop issue, but the var-tracking issue is for Alex.

[Bug target/40735] memory hog compiling big functions with -fPIE

[steven at gcc dot gnu.org]

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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
         AssignedTo|steven at gcc dot gnu.org   |unassigned at gcc dot
                   |                            |gnu.org

--- Comment #20 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-28 10:49:19 UTC ---
With release checking, the loop-doloop time is almost zero (so something is
slow in doloop checking). The var-tracking slowness does not disappear, and
dominates the compile time even more strongly:

 variable tracking       : 530.57 (84%) usr

[Bug target/40735] memory hog compiling big functions with -fPIE

[steven at gcc dot gnu.org]

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

--- Comment #21 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-28 11:29:43 UTC ---
(In reply to comment #14)
> > ~/bin/maxmem2.sh gcc-4.7 -S -o /dev/null t.i -v -std=gnu99 -Os -fPIE -fstack-protector -g --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> total: 794883 kB
> 
> we're continuing to increase, thus re-confirmed.

At r190665, with the same -min-expand=100 --param ggc-min-heapsize=131072 :

tests/test_node.c:6115:1: note: variable tracking size limit exceeded with
-fvar-tracking-assignments, retrying without
$ total: 1443401 kB