From: David Huggins-Daines <dhuggins@cs.cmu.edu>
To: openembedded-devel@openembedded.org
Subject: uclibc build failure on armv4t with -mthumb (internal compiler error)
Date: Fri, 03 Apr 2009 16:54:59 -0400 [thread overview]
Message-ID: <49D677A3.2070702@cs.cmu.edu> (raw)
I'm having trouble building uclibc in thumb mode for armv4t. It is
getting an internal compiler error when compiling ldso. The error
message is:
NOTE: make STRIPTOOL=true LD=arm-angstrom-linux-uclibcgnueabi-ld
LOCALE_DATA_FILENAME=uClibc-locale-030818.arm.tgz CC=ccache
arm-angstrom-linux-uclibcgnueabi-gcc -march=armv4t -mtune=arm920t
-mthumb-interwork -mthumb
HOSTCFLAGS=-I/home/dhuggins/Projects/TeRK/oe/tmp/staging/x86_64-linux/usr/include
CC ldso/ldso/ldso.oS
ldso/ldso/dl-elf.c: In function '_dl_dprintf':
ldso/ldso/dl-elf.c:913: error: unable to find a register to spill in
class 'LO_REGS'
ldso/ldso/dl-elf.c:913: error: this is the insn:
(insn 121 120 122 6 (set (reg/f:SI 406)
(plus:SI (reg/f:SI 25 sfp)
(reg:SI 405))) 5 {*thumb_addsi3} (nil)
(expr_list:REG_DEAD (reg:SI 405)
(nil)))
ldso/ldso/dl-elf.c:913: confused by earlier errors, bailing out
make: *** [ldso/ldso/ldso.oS] Error 1
FATAL: oe_runmake failed
I'm using the stable/2009 branch and this is GCC 4.2.4-r5
I believe there were some patches for this recently (in particular,
building ldso with -O0) but I'm still getting the error - note that it
is in a different function than the one seen earlier.
I worked around this by forcing ldso to compile with the ARM instruction
set, but I'm not sure if this is the right approach or not.
next reply other threads:[~2009-04-03 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 20:54 David Huggins-Daines [this message]
2009-04-06 19:32 ` uclibc build failure on armv4t with -mthumb (internal compiler error) Khem Raj
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=49D677A3.2070702@cs.cmu.edu \
--to=dhuggins@cs.cmu.edu \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.