public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "plessl at tik dot ee dot ethz dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19636] Can't compile ethernut OS (avr-gcc)
Date: Tue, 17 Oct 2006 14:43:00 -0000 [thread overview]
Message-ID: <20061017144312.17330.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19636-10005@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
------- Comment #14 from plessl at tik dot ee dot ethz dot ch 2006-10-17 14:43 -------
(In reply to comment #13)
> Can you try using GCC 4.1.1 and see if you can still reproduce this bug? That
> would be very informative.
Yes, the bug is still present in gcc-4.1.1, see below. I also had problems
building gcc-4.1.1 for avr. libssp doesn't compile for this target, hence I had
to disable it by passing --disable-libssp to configure.
usart.c: In function ‘UsartIOCtl’:
usart.c:821: error: unable to find a register to spill in class
‘BASE_POINTER_REGS’
usart.c:821: error: this is the insn:
(insn 663 162 163 14 (set (mem/c:HI (plus:HI (reg/f:HI 28 r28)
(const_int 1 [0x1])) [27 S2 A8])
(reg:HI 24 r24)) 12 {*movhi} (nil)
(nil))
usart.c:821: confused by earlier errors, bailing out
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19636
next prev parent reply other threads:[~2006-10-17 14:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19636-10005@http.gcc.gnu.org/bugzilla/>
2005-12-05 18:34 ` berndtrog at yahoo dot com
2006-10-11 8:44 ` plessl at tik dot ee dot ethz dot ch
2006-10-11 17:05 ` eweddington at cso dot atmel dot com
2006-10-17 14:43 ` plessl at tik dot ee dot ethz dot ch [this message]
2006-10-27 10:31 ` yuecelm at ee dot ethz dot ch
2007-04-09 21:14 ` eweddington at cso dot atmel dot com
2007-05-21 16:03 ` eweddington at cso dot atmel dot com
2007-05-21 16:10 ` [Bug target/19636] [4.0/4.1/4.2 regression] Can't compile large switch statement eweddington at cso dot atmel dot com
2007-05-21 16:17 ` eweddington at cso dot atmel dot com
2007-05-30 18:59 ` eweddington at cso dot atmel dot com
2008-03-15 0:40 ` jsm28 at gcc dot gnu dot org
2008-03-15 0:54 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:35 ` [Bug target/19636] [4.1/4.2 " jsm28 at gcc dot gnu dot org
2008-07-04 22:46 ` [Bug target/19636] [4.2 " jsm28 at gcc dot gnu dot org
2008-09-14 12:53 ` aesok at gcc dot gnu dot org
2009-03-30 15:39 ` jsm28 at gcc dot gnu dot org
2005-01-26 10:59 [Bug target/19636] New: Can't compile ethernut OS (avr-gcc) dieterbmeier at yahoo dot com
2005-01-26 11:00 ` [Bug target/19636] " dieterbmeier at yahoo dot com
2005-01-26 12:02 ` pinskia at gcc dot gnu dot org
2005-02-10 22:06 ` ericw at evcohs dot com
2005-02-10 22:59 ` ericw at evcohs dot com
2005-02-11 0:47 ` dieterbmeier at yahoo dot com
2005-02-11 0:56 ` ericw at evcohs dot com
2005-02-11 1:04 ` dieterbmeier at yahoo dot com
2005-02-13 17:58 ` andrewhutchinson at cox dot net
2005-02-13 18:14 ` andrewhutchinson at cox dot net
2005-02-18 23:42 ` berndtrog at yahoo dot com
2005-02-22 16:58 ` dieterbmeier at yahoo dot com
2005-04-30 17:41 ` berndtrog at yahoo dot com
2005-05-05 18:09 ` ericw at evcohs dot com
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=20061017144312.17330.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).