public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/60040] AVR: error: unable to find a register to spill in class 'POINTER_REGS'
Date: Tue, 18 Feb 2014 08:12:00 -0000 [thread overview]
Message-ID: <bug-60040-4-0vu9skEH9q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60040-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60040
--- Comment #3 from Sebastian Huber <sebastian.huber@embedded-brains.de> ---
With avr-rtems4.11-gcc (GCC) 4.9.0 20140218 (experimental) I still get the
error:
avr-rtems4.11-gcc -fpreprocessed -w -mmcu=atmega128 -O2 -s test.i -o /dev/null
test.i: In function 'rtems_fdisk_recycle_segment':
test.i:107:1: error: unable to find a register to spill in class 'POINTER_REGS'
}
^
test.i:107:1: error: this is the insn:
(insn 30 29 31 2 (set (reg:HI 26 r26)
(reg/v/f:HI 51 [ dpd ])) test.i:95 82 {*movhi}
(nil))
test.i:107:1: internal compiler error: in spill_failure, at reload1.c:2106
0x825135 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/sh/archive/gcc-git/gcc/rtl-error.c:109
0x81a888 spill_failure
/home/sh/archive/gcc-git/gcc/reload1.c:2106
0x81a888 find_reload_regs
/home/sh/archive/gcc-git/gcc/reload1.c:2032
0x8230a7 select_reload_regs
/home/sh/archive/gcc-git/gcc/reload1.c:2052
0x8230a7 reload(rtx_def*, int)
/home/sh/archive/gcc-git/gcc/reload1.c:973
0x72c04d do_reload
/home/sh/archive/gcc-git/gcc/ira.c:5469
0x72c04d rest_of_handle_reload
/home/sh/archive/gcc-git/gcc/ira.c:5598
0x72c04d execute
/home/sh/archive/gcc-git/gcc/ira.c:5627
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
The output is different though.
next prev parent reply other threads:[~2014-02-18 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 11:13 [Bug target/60040] New: " sebastian.huber@embedded-brains.de
2014-02-03 11:13 ` [Bug target/60040] " sebastian.huber@embedded-brains.de
2014-02-17 16:41 ` [Bug other/60040] " gjl at gcc dot gnu.org
2014-02-18 8:12 ` sebastian.huber@embedded-brains.de [this message]
2014-02-18 10:35 ` gjl at gcc dot gnu.org
2014-02-18 10:50 ` gjl at gcc dot gnu.org
2014-03-17 12:38 ` amylaar at gcc dot gnu.org
2014-04-07 13:19 ` sebastian.huber@embedded-brains.de
2014-11-05 16:19 ` joel at gcc dot gnu.org
2015-10-13 12:55 ` matthijs at stdin dot nl
2015-10-13 12:56 ` matthijs at stdin dot nl
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-60040-4-0vu9skEH9q@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).