public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42536] [4.4/4.5/4.6 regression] ICE in spill_failure, at reload1.c:2141
Date: Mon, 29 Nov 2010 21:15:00 -0000 [thread overview]
Message-ID: <bug-42536-4-K920LEF8pZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42536-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42536
Vladimir Makarov <vmakarov at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vmakarov at redhat dot com
--- Comment #6 from Vladimir Makarov <vmakarov at redhat dot com> 2010-11-29 20:39:39 UTC ---
(In reply to comment #4)
> Jeff/Vlad, how hard would it be to try to split the insn into two insns instead
> of a spill failure (for insns using a MEM whose address uses more than one hard
> register) - one which forces the address into register (assuming it is
> supported) and the store (or load) which would use a simpler address form?
If it is done in reload (and imho this is the most right place to do), I think
it would be hard. It needs some person with a good knowledge of the reload.
It is also possible to do some splitting in other parts of compiler but it
would an approximate solution (it means not all such cases will be avoided
or/and it will hurt performance in general case).
next prev parent reply other threads:[~2010-11-29 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42536-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 11:52 ` jakub at gcc dot gnu.org
2010-11-29 20:15 ` jakub at gcc dot gnu.org
2010-11-29 20:40 ` law at redhat dot com
2010-11-29 21:15 ` vmakarov at redhat dot com [this message]
2011-04-16 10:34 ` [Bug target/42536] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org
2012-01-24 5:09 ` pinskia at gcc dot gnu.org
2012-01-24 5:42 ` pinskia at gcc dot gnu.org
2012-03-13 14:32 ` [Bug target/42536] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 11:10 ` rguenth at gcc dot gnu.org
2012-09-02 9:23 ` [Bug target/42536] [4.6/4.7/4.8 " ubizjak at gmail dot com
2012-09-02 9:45 ` ubizjak at gmail dot com
2012-11-11 21:35 ` [Bug target/42536] [4.6/4.7 " steven at gcc dot gnu.org
2013-04-12 15:17 ` [Bug target/42536] [4.7 " jakub at gcc dot gnu.org
2014-06-12 12:55 ` rguenth at gcc dot gnu.org
2009-12-29 12:41 [Bug target/42536] New: [4.4/4.5 " debian-gcc at lists dot debian dot org
2010-04-30 8:58 ` [Bug target/42536] [4.4/4.5/4.6 " jakub 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-42536-4-K920LEF8pZ@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).