public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/43290] ICE in dwarf2out_frame_debug_expr
Date: Tue, 09 Mar 2010 22:39:00 -0000 [thread overview]
Message-ID: <20100309223934.32290.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43290-87@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from hjl dot tools at gmail dot com 2010-03-09 22:39 -------
(In reply to comment #9)
> (In reply to comment #8)
> > Created an attachment (id=20044)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20044&action=view) [edit]
> > gcc44-pr43290-2.patch
> >
> > Another fix. Wonder why that insn is marked as frame related at all, for the
> > drap saving the spill (and restore) generated by
> > ix86_expand_prologue/ix86_expand_epilogue should be the canonical one, after
> > all where the vDRAP was spilled to is something that could be clobbered before
> > the epilogue if vDRAP starts living in the register again, etc.
> >
>
> There may be a reason to do so at the time. If there are no
> regressions in gcc testsuite, it probably is OK not to mark
> drap as frame related.
>
It is for PR 36728.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43290
next prev parent reply other threads:[~2010-03-09 22:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 14:45 [Bug debug/43290] New: " jakub at gcc dot gnu dot org
2010-03-08 15:03 ` [Bug debug/43290] " hjl dot tools at gmail dot com
2010-03-08 15:13 ` jakub at gcc dot gnu dot org
2010-03-08 15:27 ` hjl dot tools at gmail dot com
2010-03-08 15:44 ` jakub at gcc dot gnu dot org
2010-03-08 15:48 ` hjl dot tools at gmail dot com
2010-03-08 16:38 ` jakub at gcc dot gnu dot org
2010-03-08 16:39 ` jakub at gcc dot gnu dot org
2010-03-08 16:46 ` jakub at gcc dot gnu dot org
2010-03-08 16:58 ` hjl dot tools at gmail dot com
2010-03-08 17:01 ` jakub at gcc dot gnu dot org
2010-03-09 18:49 ` jakub at gcc dot gnu dot org
2010-03-09 19:01 ` jakub at gcc dot gnu dot org
2010-03-09 22:39 ` hjl dot tools at gmail dot com [this message]
2010-03-09 22:44 ` hjl dot tools at gmail dot com
2010-03-09 22:54 ` jakub at gcc dot gnu dot org
2010-03-10 0:33 ` jakub at gcc dot gnu dot org
2010-03-10 5:38 ` hjl dot tools at gmail dot com
2010-03-10 8:07 ` jakub at gcc dot gnu dot org
2010-03-10 18:17 ` jakub at gcc dot gnu dot org
[not found] <bug-43290-4@http.gcc.gnu.org/bugzilla/>
2011-03-04 21:54 ` dirtyepic at gentoo dot org
2011-03-09 2:28 ` dirtyepic at gentoo dot org
2011-10-07 1:39 ` dirtyepic at gentoo 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=20100309223934.32290.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: 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).