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 11:26:28 +0000 [thread overview] Message-ID: <bug-99663-4-q4L454p5uH@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 #3 from Matthias Klose <doko at debian dot org> --- trying to reproduce, it ICEs at a different place... $ cat decNumber.i typedef struct { int exponent; unsigned short lsu[]; } decNumber; char __decd2utable[] = {}; decNumber *decExpOp_rhs; void decExpOp() { decNumber buft[0]; decNumber allocbuft; decNumber *t = buft; int t_0; if (decExpOp_rhs) t = &allocbuft; for (;;) { unsigned short varbuff[0]; unsigned short *msu1, *source = t->lsu + (9 ? __decd2utable[t_0] : 3); for (; source >= t->lsu; source--, msu1--) *msu1 = *source; for (; msu1 >= varbuff;) ; if (t->exponent) break; } } $ build/gcc/xgcc -Bbuild/gcc/ -c -mtune=z15 -march=z13 -mzarch -O1 decNumber.i during RTL pass: reload decNumber.i: In function ‘decExpOp’: decNumber.i:24:1: internal compiler error: in lra_set_insn_recog_data, at lra.c:1004 24 | } | ^ 0x1ea6333 lra_set_insn_recog_data(rtx_insn*) ../../src/gcc/lra.c:1004 0x1ea2063 lra_get_insn_recog_data ../../src/gcc/lra-int.h:487 0x1ea9f99 lra_update_insn_regno_info(rtx_insn*) ../../src/gcc/lra.c:1625 0x1eab8b7 lra_push_insn_1 ../../src/gcc/lra.c:1780 0x1eab905 lra_push_insn(rtx_insn*) ../../src/gcc/lra.c:1788 0x1eabad9 push_insns ../../src/gcc/lra.c:1831 0x1eabd81 lra_process_new_insns(rtx_insn*, rtx_insn*, rtx_insn*, char const*) ../../src/gcc/lra.c:1871 0x1ed2bab curr_insn_transform ../../src/gcc/lra-constraints.c:4669 0x1ed5c17 lra_constraints(bool) ../../src/gcc/lra-constraints.c:5163 0x1eaddb3 lra(_IO_FILE*) ../../src/gcc/lra.c:2336 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.
next prev parent reply other threads:[~2021-03-19 11:26 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 [this message] 2021-03-19 11:27 ` doko at debian dot org 2021-03-19 12:02 ` doko at debian dot org 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-q4L454p5uH@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: linkBe 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).