This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 29 Aug 2011 10:48:39 +0000
- Subject: [Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140
- Auto-submitted: auto-generated
- References: <bug-50203-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 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).