From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7921 invoked by alias); 22 Feb 2009 14:46:18 -0000 Received: (qmail 7818 invoked by uid 48); 22 Feb 2009 14:46:04 -0000 Date: Sun, 22 Feb 2009 14:46:00 -0000 Message-ID: <20090222144604.7817.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/37709] [4.4 Regression] inlining causes explosion in debug info In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hubicka at gcc dot gnu dot org" 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: 2009-02/txt/msg01939.txt.bz2 ------- Comment #13 from hubicka at gcc dot gnu dot org 2009-02-22 14:46 ------- There are obviously giant trees of blocks that have all variables unused and no statements in them coming from the early inliner. I am getting convinced we can safely prune those even at -g3: user can not breakpoint into the block in any way and can't ask for the value.... So I guess we could be at -g eliminating inner blocks with no used variables and no statements just keeping around blocks with statements including the unused vars so we can get proper "optimized out" debugger info. I will prepare patch for this. Honza -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37709