This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/37709] [4.4 Regression] inlining causes explosion in debug info
- From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Feb 2009 14:46:04 -0000
- Subject: [Bug tree-optimization/37709] [4.4 Regression] inlining causes explosion in debug info
- References: <bug-37709-12544@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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