[Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140

2012-01-18 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140

2011-08-29 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203 Jakub Jelinek changed: What|Removed |Added CC||aoliva at gcc dot gnu.org,

[Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140

2011-08-29 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203 --- Comment #2 from Richard Guenther 2011-08-29 10:12:00 UTC --- Shouldn't we limit the max of the param then?

[Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140

2011-08-29 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203 --- Comment #3 from Jakub Jelinek 2011-08-29 10:48:39 UTC --- But what would be a good limit for the parameter? On some targets some people have managed to trigger it even with the parameter 20 which has been the default for a while, but on othe

[Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140

2011-08-29 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203 --- Comment #4 from Richard Guenther 2011-08-29 11:05:19 UTC --- (In reply to comment #3) > But what would be a good limit for the parameter? On some targets some people > have managed to trigger it even with the parameter 20 which has been the