public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105911] New: [13 Regression] ICE: in extract_insn, at recog.cc:2791 (error: unrecognizable insn)
Date: Thu, 09 Jun 2022 17:31:13 +0000	[thread overview]
Message-ID: <bug-105911-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105911
           Summary: [13 Regression] ICE: in extract_insn, at recog.cc:2791
                    (error: unrecognizable insn)
           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: asolokha at gmx dot com
  Target Milestone: ---
            Target: x86_64-unknown-linux-gnu

gcc 13.0.0 20220605 snapshot (g:ad6919374beafac4ec1a2f8059620f261019b02f) ICEs
when compiling the following testcase w/ -O1:

__int128 v;

void
bar (__int128, __int128);

void
foo (void)
{
  bar (v /= v, v >> (v &= 0x100000001));
}

% x86_64-unknown-linux-gnu-gcc-13.0.0 -O1 yhk2zj2p.c
yhk2zj2p.c: In function 'foo':
yhk2zj2p.c:10:1: error: unrecognizable insn:
   10 | }
      | ^
(insn 20 8 21 2 (parallel [
            (set (reg:DI 94)
                (and:DI (subreg:DI (reg:TI 82 [ v.0_1 ]) 0)
                    (const_int 4294967297 [0x100000001])))
            (clobber (reg:CC 17 flags))
        ]) "yhk2zj2p.c":9:3 -1
     (nil))
during RTL pass: subreg3
yhk2zj2p.c:10:1: internal compiler error: in extract_insn, at recog.cc:2791
0x7258ef _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220605/work/gcc-13-20220605/gcc/rtl-error.cc:108
0x72590b _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220605/work/gcc-13-20220605/gcc/rtl-error.cc:116
0x723f05 extract_insn(rtx_insn*)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220605/work/gcc-13-20220605/gcc/recog.cc:2791
0x1dbab37 decompose_multiword_subregs
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220605/work/gcc-13-20220605/gcc/lower-subreg.cc:1555
0x1dbbafd execute
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220605/work/gcc-13-20220605/gcc/lower-subreg.cc:1818

             reply	other threads:[~2022-06-09 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 17:31 asolokha at gmx dot com [this message]
2022-06-09 18:00 ` [Bug target/105911] " jakub at gcc dot gnu.org
2022-06-10 10:34 ` jakub at gcc dot gnu.org
2022-06-13  8:54 ` cvs-commit at gcc dot gnu.org
2022-06-13  9:04 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105911-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).