public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rpjday at mindspring dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/24445]  New: "unable to find a register to spill in class 'R0_REGS"
Date: Wed, 19 Oct 2005 17:32:00 -0000	[thread overview]
Message-ID: <bug-24445-9738@http.gcc.gnu.org/bugzilla/> (raw)

trying to build a cross-compile toolchain using "crosstool" with the following
properties:

BINUTILS_DIR=binutils-2.16.1
GCC_DIR=gcc-4.1-20051015
GLIBC_DIR=glibc-2.3.5
LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0
GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.5

TARGET=sh4-unknown-linux-gnu
TARGET_CFLAGS="-O -m4 -ml"
GLIBC_CONFIGPARMS="no-z-defs=yes"
GLIBC_EXTRA_CONFIG="--without-fp"
USE_SYSROOT=1

  eventually, trying to compile glibc-2.3.5:

sh4-unknown-linux-gnu-gcc  ../sysdeps/generic/strtok.c -c -std=gnu99 -O -Wall
-Winline -Wstrict-prototypes -Wwrite-strings -m4 -ml   -fPIC    -I../include
-I.
-I/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc/string
-I.. -I../libio 
-I/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc
-I../sysdeps/sh/elf -I../linuxthreads/sysdeps/unix/sysv/linux/sh
-I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread
-I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv
-I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/sh
-I../sysdeps/unix/sysv/linux/sh/sh4 -I../sysdeps/unix/sysv/linux/sh
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/sh -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/sh/sh4
-I../sysdeps/sh -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/flt-32
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754 -I../sysdeps/generic/elf
-I../sysdeps/generic -nostdinc -isystem
/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/gcc-core-prefix/lib/gcc/sh4-unknown-linux-gnu/4.1.0/include
-isystem /home/rpjday/ct/sh4/sh4-unknown-linux-gnu/sys-root/usr/include
-D_LIBC_REENTRANT -include ../include/libc-symbols.h  -DPIC -DSHARED     -o
/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc/string/strtok.os
-MD -MP -MF
/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc/string/strtok.os.dt
-MT
/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc/string/strtok.os
../sysdeps/generic/strtok.c: In function 'strtok':
../sysdeps/generic/strtok.c:66: error: unable to find a register to spill in
class 'R0_REGS'
../sysdeps/generic/strtok.c:66: error: this is the insn:
(insn 68 112 69 5 (set (mem/c/i:SI (plus:SI (reg:SI 12 r12)
                (reg/f:SI 1 r1 [177])) [0 olds+0 S4 A32])
        (reg:SI 0 r0)) 172 {movsi_ie} (insn_list:REG_DEP_TRUE 62
(insn_list:REG_DEP_TRUE 67 (nil)))
    (expr_list:REG_DEAD (reg:SI 0 r0)
        (expr_list:REG_DEAD (reg/f:SI 1 r1 [177])
            (nil))))
../sysdeps/generic/strtok.c:66: internal compiler error: in spill_failure, at
reload1.c:1890
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: ***
[/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc/string/strtok.os]
Error 1
make[2]: Leaving directory
`/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/glibc-2.3.5/string'
make[1]: *** [string/subdir_lib] Error 2
make[1]: Leaving directory
`/home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/glibc-2.3.5'
make: *** [lib] Error 2


-- 
           Summary: "unable to find a register to spill in class 'R0_REGS"
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rpjday at mindspring dot com
  GCC host triplet: i686-pc-linux
GCC target triplet: sh4-unknown-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24445


             reply	other threads:[~2005-10-19 17:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 17:32 rpjday at mindspring dot com [this message]
2005-10-19 19:07 ` [Bug target/24445] " pinskia at gcc dot gnu dot org
2005-10-19 19:09 ` rpjday at mindspring dot com
2005-10-19 19:54 ` rpjday at mindspring dot com
2005-10-20 12:12 ` kkojima at gcc dot gnu dot org
2005-10-20 12:14 ` sieb at sscd dot de
2005-10-20 12:45 ` rpjday at mindspring dot com
2005-10-21 14:15 ` rpjday at mindspring dot com
2005-10-22 21:36 ` rpjday at mindspring dot com
2005-10-30  9:56 ` rpjday at mindspring dot com
2005-11-01 23:55 ` kkojima at gcc dot gnu dot org
2005-11-01 23:58 ` [Bug target/24445] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-11-03  6:39 ` mmitchel at gcc dot gnu dot org
2005-11-11  2:12 ` kkojima at gcc dot gnu dot org
2005-11-11 17:43 ` 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=bug-24445-9738@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).