public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/37709] [4.4 Regression] inlining causes explosion in debug info Date: Sun, 22 Feb 2009 14:46:00 -0000 [thread overview] Message-ID: <20090222144604.7817.qmail@sourceware.org> (raw) In-Reply-To: <bug-37709-12544@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2009-02-22 14:46 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-01 23:42 [Bug c/37709] New: cc1: out of memory regehr at cs dot utah dot edu 2008-10-01 23:43 ` [Bug c/37709] " regehr at cs dot utah dot edu 2008-10-01 23:49 ` [Bug tree-optimization/37709] [4.4 Regression] inliner gone crazy pinskia at gcc dot gnu dot org 2008-10-02 11:08 ` rguenth at gcc dot gnu dot org 2008-10-02 12:57 ` rguenth at gcc dot gnu dot org 2008-10-02 13:03 ` rguenth at gcc dot gnu dot org 2008-10-02 14:28 ` jakub at gcc dot gnu dot org 2008-10-22 3:13 ` mmitchel at gcc dot gnu dot org 2008-11-11 20:11 ` hubicka at gcc dot gnu dot org 2008-11-22 17:35 ` steven at gcc dot gnu dot org 2009-02-03 16:28 ` [Bug tree-optimization/37709] [4.4 Regression] inlining causes explosion in debug info bonzini at gnu dot org 2009-02-04 7:04 ` bonzini at gnu dot org 2009-02-12 10:29 ` hubicka at ucw dot cz 2009-02-22 14:23 ` hubicka at gcc dot gnu dot org 2009-02-22 14:23 ` hubicka at gcc dot gnu dot org 2009-02-22 14:46 ` hubicka at gcc dot gnu dot org [this message] 2009-02-23 13:11 ` hubicka at gcc dot gnu dot org 2009-02-23 13:12 ` hubicka at gcc dot gnu dot 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=20090222144604.7817.qmail@sourceware.org \ --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: linkBe 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).