[Bug target/105825] New: [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx

[Bug target/105825] New: [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx

[zsojka at seznam dot cz]

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

            Bug ID: 105825
           Summary: [13 Regression] ICE: in extract_insn, at recog.cc:2791
                    (unrecognizable insn) with -mavx
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

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

This seems to be a recent regression:
r13-912 OK
r13-960 FAIL
maybe caused by dcfdd2851b297e0005a8490b7f867ca45d1ad340

$ x86_64-pc-linux-gnu-gcc -O -mavx testcase.ctestcase.c: In function 'foo':
testcase.c:8:1: error: unrecognizable insn:
    8 | }
      | ^
(insn 15 10 16 2 (parallel [
            (set (reg:SI 93)
                (and:SI (reg:DI 90)
                    (const_int 1 [0x1])))
            (clobber (reg:CC 17 flags))
        ]) "testcase.c":7:5 -1
     (nil))
during RTL pass: subreg3
testcase.c:8:1: internal compiler error: in extract_insn, at recog.cc:2791
0x772a3a _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /repo/gcc-trunk/gcc/rtl-error.cc:108
0x772abd _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /repo/gcc-trunk/gcc/rtl-error.cc:116
0x76136f extract_insn(rtx_insn*)
        /repo/gcc-trunk/gcc/recog.cc:2791
0x24700b7 decompose_multiword_subregs
        /repo/gcc-trunk/gcc/lower-subreg.cc:1555
0x24711dd execute
        /repo/gcc-trunk/gcc/lower-subreg.cc:1818
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r13-960-20220602111723-g72c605eea94-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--disable-bootstrap --with-cloog --with-ppl --with-isl
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-960-20220602111723-g72c605eea94-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20220602 (experimental) (GCC)

[Bug target/105825] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx

[jakub at gcc dot gnu.org]

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
   Last reconfirmed|                            |2022-06-03
   Target Milestone|---                         |13.0

[Bug target/105825] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx

[jakub at gcc dot gnu.org]

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r13-927-gdcfdd2851b297e0005a8490b7f867ca45d1ad340

[Bug target/105825] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx

[cvs-commit at gcc dot gnu.org]

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:53718316afa45eb0d1c236fbbf2fc0959b08510f

commit r13-989-g53718316afa45eb0d1c236fbbf2fc0959b08510f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Jun 4 10:36:24 2022 +0200

    i386: Fix up *_doubleword_mask [PR105825]

    My PR105778 patch apparently broke the following testcase.
    If the mask has the top relevant bit clear (i.e. we know we are shifting
    by 0 to wordsize bits - 1) but doesn't have all the bits below it set,
    we emit andsi3 before the shift sequence.  When the pattern had :SI
    for that operand, that was just fine, but now that it can be also HImode
    or for -m64 DImode, we either can use a lowpart or paradoxical subreg to
    SImode as the following patch, or we use a HImode or DImode AND.
    This patch does the latter.

    2022-06-04  Jakub Jelinek  <jakub@redhat.com>

            PR target/105825
            * config/i386/i386.md (*ashl<dwi>3_doubleword_mask,
            *<insn><dwi>3_doubleword_mask): If top bit of mask is clear, but
lower
            bits of mask aren't all set, use operands[2] mode for the AND
            operation instead of always SImode.

            * gcc.dg/pr105825.c: New test.

[Bug target/105825] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx

[rguenth at gcc dot gnu.org]

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed I suppose.