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

           Summary: [4.7 Regression] ICE in extract_constrain_insn_cached,
                    at recog.c:2024
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassig...@gcc.gnu.org
        ReportedBy: dang...@gcc.gnu.org
              Host: hppa64-hp-hpux11.11
            Target: hppa64-hp-hpux11.11
             Build: hppa64-hp-hpux11.11


Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/  
-
O0  -w -c  -o 20010518-1.o
/test/gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/compile
/20010518-1.c    (timeout = 300)
/test/gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/20010518-1.c: In function
'emit_reload_insns':
/test/gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/20010518-1.c:205:1:
error:
 insn does not satisfy its constraints:
(insn 554 553 555 (set (reg:DI 1 %r1)
        (reg:DI 50 %fr22 [285]))
/test/gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/c
ompile/20010518-1.c:167 120 {*pa.md:4101}
     (nil))
/test/gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/20010518-1.c:205:1:
intern
al compiler error: in extract_constrain_insn_cached, at recog.c:2024

Numerous other similar testsuite falls, all at -O0.

-bash-3.2$ ./xgcc -B./ -v
Reading specs from ./specs
COLLECT_GCC=./xgcc
COLLECT_LTO_WRAPPER=./lto-wrapper
Target: hppa64-hp-hpux11.11
Configured with: ../gcc/configure --with-gnu-as --with-as=/opt/gnu64/bin/as
--with-ld=/usr/ccs/bin/ld --enable-shared --with-local-prefix=/opt/gnu64
--prefix=/opt/gnu64/gcc/gcc-4.6.0 --build=hppa64-hp-hpux11.11
--enable-threads=posix --disable-nls --with-gmp=/opt/gnu64/gcc/gcc-4.6.0
--with-libelf=/opt/gnu64 --enable-languages=c,c++,objc,obj-c++,fortran,lto
Thread model: posix
gcc version 4.7.0 20110330 (experimental) [trunk revision 171715] (GCC)

Probably, has to do with change in handling of cover classes.  It
is not possible to copy directly between GENERAL_REGS and FP_REGS
on PA.

Reply via email to