public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/50203] ICE: in output_loc_list, at dwarf2out.c:8188 with --param max-vartrack-expr-depth=140
Date: Mon, 29 Aug 2011 11:48:00 -0000 [thread overview]
Message-ID: <bug-50203-4-z5Qj843kk5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50203-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50203
--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 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 ...
next prev parent reply other threads:[~2011-08-29 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 22:06 [Bug debug/50203] New: " zsojka at seznam dot cz
2011-08-29 10:05 ` [Bug debug/50203] " jakub at gcc dot gnu.org
2011-08-29 10:49 ` rguenth at gcc dot gnu.org
2011-08-29 11:18 ` jakub at gcc dot gnu.org
2011-08-29 11:48 ` rguenth at gcc dot gnu.org [this message]
2012-01-19 5:52 ` pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-50203-4-z5Qj843kk5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).