I've been seeing the following SPEC ICEs on powerpc-darwin when compiling 
with "-fprofile-arcs -O2 -mpowerpc64":

==> SPEC's gap:
gcc -c -o system.o -DSYS_IS_BSD -DSYS_HAS_IOCTL_PROTO -DSYS_HAS_TIME_PROTO -
DSYS_HAS_SIGNAL_PROTO -DSYS_HAS_ANSI -DSYS_HAS_CALLOC_PROTO -
DSYS_HAS_STDIO_PROTO -fprofile-arcs -O2 -mpowerpc64  system.c

system.c: In function 'SyFopen':
system.c:688: internal compiler error: in schedule_insns, at sched-rgn.c:2549


==> SPEC's gcc:
gcc -c -o c-decl.o  -DHOST_WORDS_BIG_ENDIAN -fno-inline-functions -fprofile-
arcs -O3 -mpowerpc64  c-decl.c

c-decl.c: In function 'duplicate_decls':
c-decl.c:1860: warning: incompatible implicit declaration of built-in 
function 'memcpy'
c-decl.c: In function 'layout_array_type':
c-decl.c:5761: error: unrecognizable insn:
(insn 61 0 0 (set (reg:SI 3 r3 [ t ])
        (reg:DI 3 r3)) -1 (nil)
    (nil))
c-decl.c:5761: internal compiler error: in extract_insn, at recog.c:2042


==> SPEC's crafty:
gcc -c -o swap.o  -DLINUX_SPARC -DSPEC_CPU2000 -fprofile-arcs -O3 -mpowerpc64 
swap.c

swap.c: In function 'Swap':
swap.c:151: error: unrecognizable insn:
(insn 1033 0 0 (set (reg:SI 5 r5 [ source ])
        (reg:DI 2 r2)) -1 (nil)
    (nil))
swap.c:151: internal compiler error: in extract_insn, at recog.c:2042


The extract_insn error also shows up in other SPEC benchmarks.

I think this problem was introduced between Feb. 3rd to Feb. 15th.

This might be a duplicate of PR20203?

-- 
           Summary: SPEC ICE's on powerpc-darwin compiling with "-fprofile-
                    arcs -O2 -mpowerpc64"
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dorit at il dot ibm dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: powerpc-apple-darwin7.7.0
  GCC host triplet: powerpc-apple-darwin7.7.0
GCC target triplet: powerpc-apple-darwin7.7.0


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

Reply via email to