public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ralf dot corsepius at rtems dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16719] [ColdFire] Illegal move of byte itno address register causes compiler to ICE
Date: Fri, 28 Jan 2005 14:11:00 -0000 [thread overview]
Message-ID: <20050128141127.11171.qmail@sourceware.org> (raw)
In-Reply-To: <20040726172517.16719.peter@the-baradas.com>
------- Additional Comments From ralf dot corsepius at rtems dot org 2005-01-28 14:11 -------
The patch contained in
http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00405.html
doesn't seem to work for me, rsp. triggers another ICE, at least the error
message seems to have changed:
With today's gcc/cvs-trunk + your patch applied:
# m68k-rtems4.7-gcc -W -Wno-unused -Wshadow -m5206e -O3 -fomit-frame-pointer
-funroll-loops -S -o tmp.s /tmp/safer.c
/tmp/safer.c: In function 'safer_ecb_encrypt':
/tmp/safer.c:2494: error: unable to find a register to spill in class 'ADDR_REGS'
/tmp/safer.c:2494: error: this is the insn:
(insn 95 94 97 10 (set (reg:SI 8 %a0 [95])
(plus:SI (subreg:SI (mem/s/u:QI (plus:SI (reg/f:SI 13 %a5 [189])
(reg:SI 0 %d0 [91])) [0 safer_ebox S1 A8]) 0)
(subreg:SI (mem:QI (plus:SI (reg/v/f:SI 10 %a2 [orig:39 key.78 ] [39])
(const_int 9 [0x9])) [0 S1 A8]) 0))) 96 {*addsi3_5200}
(insn_list:REG_DEP_TRUE 91 (nil))
(expr_list:REG_DEAD (reg:SI 0 %d0 [91])
(nil)))
/tmp/safer.c:2494: internal compiler error: in spill_failure, at reload1.c:1872
Also I am seeing a new ICE during building RTEMS, but I am not sure if this is
related to your patch.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |joel at oarcorp dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16719
next prev parent reply other threads:[~2005-01-28 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 17:25 [Bug target/16719] New: " peter at the-baradas dot com
2004-07-26 17:26 ` [Bug target/16719] " peter at the-baradas dot com
2004-10-25 0:49 ` pinskia at gcc dot gnu dot org
2004-10-25 0:59 ` pinskia at gcc dot gnu dot org
2005-01-27 17:33 ` ralf dot corsepius at rtems dot org
2005-01-27 18:16 ` peter at the-baradas dot com
2005-01-28 14:11 ` ralf dot corsepius at rtems dot org [this message]
2005-07-11 23:32 ` cvs-commit at gcc dot gnu dot org
2005-07-11 23:32 ` bernie at develer dot com
2005-07-11 23:35 ` bernie at develer dot com
2005-07-26 4:49 ` cvs-commit at gcc dot gnu dot org
2005-07-26 20:32 ` cvs-commit at gcc dot gnu dot org
2005-07-26 20:38 ` pinskia 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=20050128141127.11171.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).