[Bug target/63805] ICE: in extract_insn, at recog.c:2327 with -mcpu=power8

["msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org

--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
A smaller test case still fails with GCC 5.0.0 20150221, on both ppc64 and
ppc64le.  4.9.4 and 4.8.3 fail similarly.

$ cat u.cpp && /build/gcc-trunk/gcc/xgcc -B /build/gcc-trunk/gcc -O2 -S
-mcpu=power8 -xc++ u.cpp
struct A { long a; int b; };

struct B
{
    struct { } c;
    long a;
    int b;
};

void foo (B);

void bar ()
{
    A a;
    __atomic_load (&a, &a, 0);
    foo (B ());
}
u.cpp: In function âvoid bar()â:
u.cpp:17:1: error: unrecognizable insn:
 }
 ^
(insn 5 2 6 2 (set (reg:PTI 156)
        (unspec:PTI [
                (mem/v:TI (plus:DI (reg/f:DI 150 virtual-stack-vars)
                        (const_int 24 [0x18])) [-1  S16 A128])
            ] UNSPEC_LSQ)) u.cpp:15 -1
     (nil))
u.cpp:17:1: internal compiler error: in extract_insn, at recog.c:2343
0x109b11db _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
    /home/remote/msebor/fsf/gcc/trunk/gcc/rtl-error.c:110
0x109b1247 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
    /home/remote/msebor/fsf/gcc/trunk/gcc/rtl-error.c:118
0x10977b87 extract_insn(rtx_insn*)
    /home/remote/msebor/fsf/gcc/trunk/gcc/recog.c:2343
0x106e0ddf instantiate_virtual_regs_in_insn
    /home/remote/msebor/fsf/gcc/trunk/gcc/function.c:1598
0x106e0ddf instantiate_virtual_regs
    /home/remote/msebor/fsf/gcc/trunk/gcc/function.c:1966
0x106e0ddf execute
    /home/remote/msebor/fsf/gcc/trunk/gcc/function.c:2015
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.