public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99663] [11 Regression] ICE in extract_constrain_insn, at recog.c:2670 on s390x-linux-gnu
Date: Fri, 19 Mar 2021 12:02:40 +0000	[thread overview]
Message-ID: <bug-99663-4-J8bs5wn81s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99663-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Matthias Klose <doko at debian dot org> ---
and the reduction for the original ICE:

typedef struct {
  int exponent;
  unsigned short lsu[];
} decNumber;
decNumber decDivideOp_lhs;
short decDivideOp_varbuff;
void decDivideOp(decNumber *rhs) {
  short *msu1;
  int exponent;
  unsigned short *source;
  for (; source >= decDivideOp_lhs.lsu; source--, msu1--)
    *msu1 = *source;
  for (;;)
    if (exponent)
      if (decDivideOp_varbuff)
        exponent = rhs->exponent;
}

$ build/gcc/xgcc -Bbuild/gcc/ -c -mtune=z15 -march=z13 -mzarch -O2
-fno-stack-protector -fPIC decNumber.i 
decNumber.i: In function ‘decDivideOp’:
decNumber.i:17:1: error: insn does not satisfy its constraints:
   17 | }
      | ^
(insn 7 6 2 2 (set (reg:DI 3 %r3 [69])
        (plus:DI (reg:DI 0 %r0 [77])
            (const_int 4 [0x4]))) "decNumber.i":11:17 1471 {*la_64}
     (nil))
during RTL pass: reload
decNumber.i:17:1: internal compiler error: in extract_constrain_insn, at
recog.c:2670
0x218b329 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ../../src/gcc/rtl-error.c:108
0x218b4b5 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        ../../src/gcc/rtl-error.c:118
0x20d66a1 extract_constrain_insn(rtx_insn*)
        ../../src/gcc/recog.c:2670
0x1ead125 check_rtl
        ../../src/gcc/lra.c:2087
0x1eae299 lra(_IO_FILE*)
        ../../src/gcc/lra.c:2505
0x1e13ec3 do_reload
        ../../src/gcc/ira.c:5834
0x1e145f1 execute
        ../../src/gcc/ira.c:6020
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

  parent reply	other threads:[~2021-03-19 12:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  9:33 [Bug target/99663] New: " doko at debian dot org
2021-03-19  9:51 ` [Bug target/99663] " doko at debian dot org
2021-03-19  9:58 ` jakub at gcc dot gnu.org
2021-03-19 10:07 ` rguenth at gcc dot gnu.org
2021-03-19 10:34 ` marxin at gcc dot gnu.org
2021-03-19 11:26 ` doko at debian dot org
2021-03-19 11:27 ` doko at debian dot org
2021-03-19 12:02 ` doko at debian dot org [this message]
2021-03-19 12:03 ` doko at gcc dot gnu.org
2021-03-19 12:08 ` jakub at gcc dot gnu.org
2021-03-19 12:19 ` doko at debian dot org
2021-03-19 12:44 ` jakub at gcc dot gnu.org
2021-03-19 17:24 ` vmakarov at gcc dot gnu.org
2021-03-19 19:36 ` cvs-commit at gcc dot gnu.org
2021-03-22 17:44 ` doko at debian dot 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-99663-4-J8bs5wn81s@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).