From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16601 invoked by alias); 29 Aug 2011 10:49:28 -0000 Received: (qmail 16575 invoked by uid 22791); 29 Aug 2011 10:49:26 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 29 Aug 2011 10:49:12 +0000 From: "jakub at gcc dot 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:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-08/txt/msg02285.txt.bz2 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).