public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/41993] [sh] ICE in create_pre_exit, at mode-switching.c:399
Date: Mon, 05 Nov 2012 09:14:00 -0000 [thread overview]
Message-ID: <bug-41993-4-cLqCriqcwb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41993-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41993
--- Comment #5 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2012-11-05 09:13:57 UTC ---
(In reply to comment #4)
> In -O0 case, we broke discovery loop too early, so we can't find all return
> regs. I would argue, that we should ignore non-relevant pseudos with:
You are right. I was wrong about what is going on that case.
next prev parent reply other threads:[~2012-11-05 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41993-4@http.gcc.gnu.org/bugzilla/>
2012-11-04 16:46 ` ubizjak at gmail dot com
2012-11-05 9:14 ` kkojima at gcc dot gnu.org [this message]
2012-11-05 9:17 ` ubizjak at gmail dot com
2012-11-05 10:19 ` kkojima at gcc dot gnu.org
2012-11-06 9:17 ` kkojima at gcc dot gnu.org
2012-11-06 14:31 ` uros at gcc dot gnu.org
2012-11-07 23:24 ` kkojima at gcc dot gnu.org
2012-11-08 7:24 ` ubizjak at gmail dot com
2012-11-11 22:45 ` ubizjak at gmail dot com
2012-11-12 10:35 ` kkojima at gcc dot gnu.org
2012-11-12 20:21 ` olegendo at gcc dot gnu.org
2012-11-13 17:00 ` uros at gcc dot gnu.org
2009-11-09 3:18 [Bug c/41993] New: " iwamatsu at nigauri dot org
2009-11-11 21:59 ` [Bug target/41993] " kkojima at gcc dot gnu dot org
2009-11-17 2:56 ` iwamatsu at nigauri dot org
2009-11-17 22:24 ` kkojima 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=bug-41993-4-cLqCriqcwb@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).