[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #10 from Alexandre Oliva 2011-10-19 15:50:04 UTC --- Author: aoliva Date: Wed Oct 19 15:50:00 2011 New Revision: 180194 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180194 Log: PR debug/49310 * var-tracking.c (loc_exp_dep, o

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #8 from Joost VandeVondele 2011-07-04 18:57:45 UTC --- patch ;-) Index: gcc/params.def === --- gcc/params.def (revision 175820) +++ gcc/params.def (working cop

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #7 from Joost VandeVondele 2011-06-09 06:54:33 UTC --- two more datapoints (depth=30 is still running): max-vartrack-expr-depth=22: var-tracking emit :5459.44 (99%) usr max-vartrack-expr-depth=25: var-tracking emit :42078.07

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #6 from Jakub Jelinek 2011-06-08 13:38:51 UTC --- Or alternatively make it more dynamic, like if in one function the maximum level is reached or almost reached (so it could be checked only in vt_expand_loc_callback) more than some par

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #5 from Jakub Jelinek 2011-06-08 13:34:42 UTC --- 10 was the minimal value to get reasonable debug info in some cases (e.g. gcc.dg/guality/), so perhaps 20 is too much and we should go down to the default of 12-15.

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #4 from Joost VandeVondele 2011-06-08 13:23:00 UTC --- (In reply to comment #3) > Using -g -O2 -fbounds-check instead of -g -O1 -fbounds-check cures it, > or e.g. -g -O1 -fbounds-check --param max-vartrack-expr-depth=5 > speeds it up.

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 Jakub Jelinek changed: What|Removed |Added CC||aoliva at gcc dot gnu.org,

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 --- Comment #2 from Joost VandeVondele 2011-06-08 07:16:06 UTC --- the testcase from http://gcc.gnu.org/bugzilla/attachment.cgi?id=20290 can be used more conveniently. It runs in 1.4s and still spends 50% of time in var-tracking emit. Using

[Bug middle-end/49310] [4.7 Regression] Compile time hog in var-tracking emit

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49310 Joost VandeVondele changed: What|Removed |Added Summary|[4.7 Regression] Compile|[4.7 Regression] Compile