[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-30 Thread hubicka at ucw dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #28 from Jan Hubicka --- > The recent regression is we no longer throw them away plentiful during CFG > cleanup and now they pile up during inlining. > > I agree full DCE with liveness will be expensive for usually little gain. Not

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-30 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #27 from rguenther at suse dot de --- On April 30, 2019 4:27:25 PM GMT+02:00, "aoliva at gcc dot gnu.org" wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 > >--- Comment #26 from Alexandre Oliva --- >I saw the #c11 patch

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-30 Thread aoliva at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #26 from Alexandre Oliva --- I saw the #c11 patch in gcc-patches, and it seemed to have been posted FTR and installed. It looked good, so I didn't comment on it. I agree about the effects of #c16, though I begin to get a feeling

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-30 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #25 from Jakub Jelinek --- Author: jakub Date: Tue Apr 30 07:40:06 2019 New Revision: 270674 URL: https://gcc.gnu.org/viewcvs?rev=270674=gcc=rev Log: PR tree-optimization/90273 * tree-ssa-dce.c

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-30 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #24 from Jakub Jelinek --- (In reply to Alexandre Oliva from comment #23) > > what are the rules of which ones we can remove? Can we always just keep the > last? What about location differences? What about possibly interleaving >

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread aoliva at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #23 from Alexandre Oliva --- > what are the rules of which ones we can remove? Can we always just keep the last? What about location differences? What about possibly interleaving DEBUG_BEGIN stmts? code insns and markers are

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #22 from Jan Hubicka --- gcc 8 with debug info real45m49.664s user500m1.776s sys 22m39.816s llvm 7 with debug info real43m43.798s user447m36.028s sys 10m13.512s

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #21 from Jan Hubicka --- I just built Firefox with GCC 9 branch and the updated patch. Debug enabled build is: real45m56.187s user493m8.688s sys 22m4.512s compared to debug disabled build with GCC 9: real35m5.141s

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #20 from Jakub Jelinek --- Another report: https://gcc.gnu.org/ml/gcc/2019-04/msg00270.html

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rsandifo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #19 from rsandifo at gcc dot gnu.org --- (In reply to Richard Biener from comment #18) > (In reply to rsand...@gcc.gnu.org from comment #17) > > Created attachment 46261 [details] > > Doing the removal in

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #18 from Richard Biener --- (In reply to rsand...@gcc.gnu.org from comment #17) > Created attachment 46261 [details] > Doing the removal in find_obviously_necessary_stmts > > Just for the record: I'd written this over the weekend

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rsandifo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 rsandifo at gcc dot gnu.org changed: What|Removed |Added CC||rsandifo at gcc dot

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #16 from Richard Biener --- Created attachment 46260 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46260=edit removed-unused-local patch There do appear to be variables that are just appearing in # DEBUG var => NULL stmts,

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #15 from Richard Biener --- And it's indeed "caused" by the CFG-cleanup fixes. The DCE patch gets us back to (nearly) the same number of debug stmts as before.

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Richard Biener changed: What|Removed |Added Attachment #46256|0 |1 is obsolete|

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #13 from Richard Biener --- (In reply to Richard Biener from comment #9) > Created attachment 46257 [details] > more aggressive variant > > More aggressive variant using a bitmap, simply keeping the last, does for > example > > @@

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #12 from Richard Biener --- Is # DEBUG INLINE_ENTRY NULL useful at all? And since I see # DEBUG D#1157 => _2(D)->mOffsetD.377222 # DEBUG thisD.1370683 => D#1158 # DEBUG aOtherD.1370684 => D#1157 # DEBUG INLINE_ENTRY

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #11 from Richard Biener --- I also see # DEBUG D#1 => {CLOBBER} # DEBUG grayWordD.71258 => D#1 that looks pointless. Results from removing grayWord_57(D) ={v} {CLOBBER}; during into-SSA rewrite. That should instead be #

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread hubicka at ucw dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #10 from Jan Hubicka --- Hi, the file was too large for bugzilla so I uploaded it to http://www.ucw.cz/~hubicka/Unified_cpp_dom_events0-8.ii.xz and posted link in comment #2 :) The agressive variant helps (I did not try to other

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #9 from Richard Biener --- Created attachment 46257 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46257=edit more aggressive variant More aggressive variant using a bitmap, simply keeping the last, does for example @@ -243,7

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #8

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Richard Biener changed: What|Removed |Added CC||aoliva at gcc dot gnu.org --- Comment

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Richard Biener changed: What|Removed |Added CC||rguenth at gcc dot gnu.org Target

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-28 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #4 from Jan Hubicka --- The code is: inline bool IsNodeInternal() const { return false; } template inline bool IsNodeInternal(First aFirst, Args... aArgs) const { return mNodeInfo->Equals(aFirst) ||

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-28 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Jan Hubicka changed: What|Removed |Added CC||rguenther at suse dot de --- Comment #3

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-28 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 --- Comment #2 from Jan Hubicka --- http://www.ucw.cz/~hubicka/Unified_cpp_dom_events0-8.ii.xz

[Bug debug/90273] [9/10 Regression] GCC runs out of memory building Firefox

2019-04-28 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273 Eric Gallager changed: What|Removed |Added Keywords||build, memory-hog CC|