[Bug c++/70325] New: ICE on __builtin_ia32_storedquqi256_mask

rippey.e at gmail dot com gcc-bugzilla@gcc.gnu.org
Sun Mar 20 19:29:00 GMT 2016


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

            Bug ID: 70325
           Summary: ICE on __builtin_ia32_storedquqi256_mask
           Product: gcc
           Version: 5.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rippey.e at gmail dot com
  Target Milestone: ---

Created attachment 38038
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38038&action=edit
Reduced testcase

Running gcc 5.3.0 on the attached code produces the following message:

: In function ‘int f(int, I)’:
:7:1: error: unrecognizable insn:
(insn 11 10 14 2 (set (mem:V32QI (reg/f:DI 89) [0  S32 A16])
        (vec_merge:V32QI (unspec:V32QI [
                    (reg:V32QI 90)
                ] UNSPEC_STOREU)
            (mem:V32QI (reg/f:DI 89) [0  S32 A16])
            (reg:SI 91))) :6 -1
     (nil))
:7:1: internal compiler error: in extract_insn, at recog.c:2343
0xa7ecd8 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /disk/0/erippey/gcc/objdir/../gcc-5.3.0/gcc/rtl-error.c:110
0xa7ed09 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /disk/0/erippey/gcc/objdir/../gcc-5.3.0/gcc/rtl-error.c:118
0xa4ed69 extract_insn(rtx_insn*)
        /disk/0/erippey/gcc/objdir/../gcc-5.3.0/gcc/recog.c:2343
0x8b9503 instantiate_virtual_regs_in_insn
        /disk/0/erippey/gcc/objdir/../gcc-5.3.0/gcc/function.c:1598
0x8b9503 instantiate_virtual_regs
        /disk/0/erippey/gcc/objdir/../gcc-5.3.0/gcc/function.c:1966
0x8b9503 execute
        /disk/0/erippey/gcc/objdir/../gcc-5.3.0/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.

Running on current trunk produces a similar message, as does 5.2.1.


More information about the Gcc-bugs mailing list