egcs 1.1.2/ppc: internal error--insn does not satisfy its constr
Jeffrey A Law
law@upchuck.cygnus.com
Mon May 31 00:05:00 GMT 1999
In message <XFMail.990320113926.jeremy@goop.org>you write:
> This message is in MIME format
> --_=XFMail.1.3.p0.Linux:990320113926:6412=_
> Content-Type: text/plain; charset=us-ascii
>
> Hi,
>
> I've built egcs 1.1.2 targeting powerpc-linux-gnu hosted on
> powerpc-linux-glibc1. I'm trying to build glibc 2.1 with this compiler, bu
> t I
> get:
>
> powerpc-unknown-linux-gnu-gcc ../sysdeps/unix/sysv/linux/poll.c
> -c -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -fp ic
> -I../include -I. -I/home/jeremy/r16a/main/tools/builddir/ppc/glibc/io
> -I.. -I../libio -I/home/jeremy/r16a/main/tools/bui lddir/ppc/glibc
> -I../sysdeps/powerpc/elf -I../linuxthreads/sysdeps/unix/sysv/linux
> -I../linuxthreads/sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv
> -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/powerpc
> -I../linuxthreads/sysdeps/pthread/cmpxchg -I../crypt/sysdeps/unix
> -I../sysdeps/unix/sysv/linux/powerpc -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 -I../sysdeps/posix -I../sysdeps/powerpc
> -I../sysdeps/wordsize-32 -I../sysdeps/ieee754
> -I../sysdeps/libm-ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic
> -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -o
> /home/jeremy/r16a/main/tools/builddir/ppc/glibc/io/poll.os
> ../sysdeps/unix/bsd/poll.c: In function `__emulate_poll':
> In file included from ../sysdeps/unix/sysv/linux/poll.c:62:
> ../sysdeps/unix/bsd/poll.c:121: internal error--insn does not satisfy its
> constraints:
> (insn 810 172 176 (set (reg:SI 12 r12)
> (unspec[
> (symbol_ref:SI ("@max_fd_size.39"))
> (reg:SI 65 lr)
> ] 8)) 398 {*movsi_got_internal} (nil)
> (nil))
> /home/jeremy/r16a/main/tools/gnu/gcc/toplev.c:1367: Internal compiler error
> in
> function fatal_insn
I just tried this with the gcc-2.95 prerelease CVS sources and it seems to be
working fine now. You should expect this bug to be fixed in the upcoming
gcc-2.95 release.
Thanks,
jeff
More information about the Gcc-bugs
mailing list