[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||DUPLICATE

--- Comment #5 from Andrew Pinski  2012-01-19 
05:47:40 UTC ---
This is basically a dup of bug 51695 because that is also a  >= 64KB
expression.

*** This bug has been marked as a duplicate of bug 51695 ***


[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
> default for a while, but on other code/targets even a few hundred is fine.
> As I wrote on gcc-patches I think, what we could do is just drop the 
> expression
> on the floor instead of asserting if it is >= 64KB, or we could stick it into 
> a
> DW_TAG_dwarf_procedure (though, I think >= 64KB location expressions ought to
> be rarely useful).

I suppose we can't know in advance and turn the max-vartrack-expr-depth param
into a max-dwarf2-expr-size param?  That we could limit to 64kb ...


[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 other code/targets even a few hundred is fine.
As I wrote on gcc-patches I think, what we could do is just drop the expression
on the floor instead of asserting if it is >= 64KB, or we could stick it into a
DW_TAG_dwarf_procedure (though, I think >= 64KB location expressions ought to
be rarely useful).


[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

Jakub Jelinek  changed:

   What|Removed |Added

 CC||aoliva at gcc dot gnu.org,
   ||jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek  2011-08-29 
09:08:45 UTC ---
DWARF has a fixed limit for the size of expression in .debug_loc - 64KB, so
with insane high parameters you can trigger it.