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/48866] gcc hangs when -g is set
Date: Thu, 05 May 2011 11:56:00 -0000	[thread overview]
Message-ID: <bug-48866-4-BnHHGCPIPo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48866-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48866

--- Comment #5 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2011-05-05 11:54:12 UTC ---
I think the problem is that the debug stmts are being expanded into debug insns
*before* the code that should precede them.  If we expanded the stmts in the
natural, expended order, we'd get the variables bound to simpler expressions. 
That said, I'm not sure this will avoid the cselib slowdown, for we will likely
end up having to use the mems as a location.  Investigating...


  parent reply	other threads:[~2011-05-05 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04  8:56 [Bug debug/48866] New: " siebert at aicas dot com
2011-05-04 10:37 ` [Bug debug/48866] " paolo.carlini at oracle dot com
2011-05-04 11:43 ` rguenth at gcc dot gnu.org
2011-05-04 12:08 ` jakub at gcc dot gnu.org
2011-05-04 14:28 ` jakub at gcc dot gnu.org
2011-05-05 11:56 ` aoliva at gcc dot gnu.org [this message]
2011-05-05 13:06 ` aoliva at gcc dot gnu.org
2011-05-05 13:55 ` jakub at gcc dot gnu.org
2011-05-06 14:45 ` aoliva at gcc dot gnu.org
2011-05-06 22:30 ` aoliva at gcc dot gnu.org
2011-05-07  6:16 ` jakub at gcc dot gnu.org
2011-05-07  6:37 ` jakub at gcc dot gnu.org
2012-04-13 15:57 ` aoliva at gcc dot gnu.org
2012-06-13 20:42 ` aoliva at gcc dot gnu.org
2012-06-28  7:40 ` 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-48866-4-BnHHGCPIPo@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: link
Be 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).