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: Fri, 06 May 2011 22:30:00 -0000 [thread overview]
Message-ID: <bug-48866-4-dcqPv2R5To@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
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #24189|0 |1
is obsolete| |
--- Comment #9 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2011-05-06 22:18:16 UTC ---
Created attachment 24202
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24202
Avoid too-complex value exprs by keeping unreplaced replaceable expansions in
natural order
This alternate patch implements (with minor changes) the plan described in
comment 8, that should improve debuggability and limit the complexity of debug
values generated by the expander to about the maximum complexity of an insn.
It successfully undoes the code movement of TER for code generated that is not
combined into other stmts. force_reg for a subsequent insn is still regarded
as combination, although I have plans to move that up as well. Using the
suggested target for an assignment is regarded as combination, and it must
remain that way to avoid moving the assignment before the initialization of the
target.
This has so far passed compare after bootstrap-debug on x86_64-linux-gnu;
testing it more thoroughly now. Will add comments before posting it to the
list.
next prev parent reply other threads:[~2011-05-06 22:30 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
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 [this message]
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-dcqPv2R5To@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).