public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/47106] -fcompare-debug failure (length) with -fpartial-inlining -flto -fconserve-stack Date: Thu, 30 Dec 2010 20:15:00 -0000 [thread overview] Message-ID: <bug-47106-4-Dq7OdZR82r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47106-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47106 --- Comment #2 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2010-12-30 20:15:22 UTC --- Created attachment 22870 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22870 Patch that fixes the bug, regstrapping When estimating the stack size of a function, we shouldn't set TREE_USED in the loop over local decls, for this makes us count every block var that is local when accounting block vars: since we preserve more block vars for debugging purposes, we end up counting them all in the latter pass, even if they weren't marked as TREE_USED before the loop over locals. Simply removing the set would be enough to fix the bug, but I figured we'd get more accurate results if we refrained from counting variables twice, so I added a bitmap. This fixes the bug, testing a bootstrap with these flags now.
next prev parent reply other threads:[~2010-12-30 20:15 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-29 11:41 [Bug debug/47106] New: " zsojka at seznam dot cz 2010-12-30 20:09 ` [Bug debug/47106] " aoliva at gcc dot gnu.org 2010-12-30 20:15 ` aoliva at gcc dot gnu.org [this message] 2011-01-21 15:17 ` aoliva at gcc dot gnu.org 2011-01-21 15:40 ` aoliva at gcc dot gnu.org 2011-01-21 22:36 ` aoliva at gcc dot gnu.org 2011-01-31 8:07 ` aoliva at gcc dot gnu.org 2011-01-31 11:55 ` aoliva at gcc dot gnu.org 2011-02-02 5:44 ` aoliva at gcc dot gnu.org 2011-02-02 6:18 ` aoliva at gcc dot gnu.org 2011-02-02 6:28 ` aoliva at gcc dot gnu.org 2011-02-15 18:36 ` aoliva at gcc dot gnu.org 2011-02-15 18:37 ` aoliva at gcc dot gnu.org 2011-02-15 18:37 ` aoliva at gcc dot gnu.org 2011-02-15 18:38 ` aoliva at gcc dot gnu.org 2011-02-17 16:24 ` hubicka at gcc dot gnu.org 2011-02-21 14:22 ` danglin at gcc dot gnu.org 2011-02-21 16:06 ` jakub at gcc dot gnu.org 2011-02-23 0:47 ` aoliva 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-47106-4-Dq7OdZR82r@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: 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).