[Bug target/69146] [5 Regression] ICE in extract_insn, at recog.c:2343 on powerpc64le-linux-gnu

msebor at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Sun Jan 24 22:36:00 GMT 2016


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69146

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2016-01-24
                 CC|                            |msebor at gcc dot gnu.org
     Ever confirmed|0                           |1
      Known to fail|                            |6.0

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed with last week's trunk. Big endian powerpc64 doesn't fail.  Here's a
slightly simplified test case:

$ cat t.c && /build/gcc-trunk/gcc/xgcc -B /build/gcc-trunk/gcc -O2 -S -Wall
-Wextra -xc++ t.c
short a;

bool foo (short b)
{
   __sync_bool_compare_and_swap (&a, -1, b);
}


t.c: In function ‘bool foo(short int)’:
t.c:6:1: warning: no return statement in function returning non-void
[-Wreturn-type]
 }
 ^

t.c:6:1: error: unrecognizable insn:
(insn 10 9 11 4 (set (reg:CC 163)
        (compare:CC (reg:SI 162)
            (const_int 65535 [0xffff]))) t.c:5 -1
     (nil))
t.c:6:1: internal compiler error: in extract_insn, at recog.c:2286
0x10f7ae2f _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /src/gcc/trunk/gcc/rtl-error.c:108
0x10f7aea7 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /src/gcc/trunk/gcc/rtl-error.c:116
0x10eff25f extract_insn(rtx_insn*)
        /src/gcc/trunk/gcc/recog.c:2286
0x10af73bb instantiate_virtual_regs_in_insn
        /src/gcc/trunk/gcc/function.c:1582
0x10af914b instantiate_virtual_regs
        /src/gcc/trunk/gcc/function.c:1950
0x10af92bb execute
        /src/gcc/trunk/gcc/function.c:1999
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


More information about the Gcc-bugs mailing list