public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99461] New: [11 Regression] ICE in extract_constrain_insn, at recog.c:2670 since r11-7526-g9105757a59b89019 Date: Mon, 08 Mar 2021 10:49:20 +0000 [thread overview] Message-ID: <bug-99461-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99461 Bug ID: 99461 Summary: [11 Regression] ICE in extract_constrain_insn, at recog.c:2670 since r11-7526-g9105757a59b89019 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: vmakarov at redhat dot com Target Milestone: --- Host: x86_64-linux-gnu The following fails, it's reduced from qemu package: $ cat qemu.i struct saveBDAstate { short vbe_mode; }; void __set_seg_ES(); struct saveBDAstate bda_save_restore(struct saveBDAstate *data) { struct saveBDAstate *info = data; __set_seg_ES(); __asm__("" : "=m"(info->vbe_mode)); __asm__("" : : ""(info)); } $ gcc qemu.i -Os -m16 -S qemu.i: In function ‘bda_save_restore’: qemu.i:12:1: error: unrecognizable insn: 12 | } | ^ (insn 8 7 9 2 (parallel [ (set (mem:HI (mem/f/c:SI (plus:SI (reg/f:SI 6 bp) (const_int 12 [0xc])) [3 data+0 S4 A32]) [2 data_1(D)->vbe_mode+0 S2 A16]) (asm_operands:HI ("") ("=m") 0 [] [] [] qemu.i:10)) (clobber (reg:CC 17 flags)) ]) "qemu.i":10:3 -1 (nil)) during RTL pass: reload qemu.i:12:1: internal compiler error: in extract_constrain_insn, at recog.c:2670 0x6ff1e1 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /home/marxin/Programming/gcc/gcc/rtl-error.c:108 0x6ff203 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /home/marxin/Programming/gcc/gcc/rtl-error.c:116 0x6fd485 extract_constrain_insn(rtx_insn*) /home/marxin/Programming/gcc/gcc/recog.c:2670 0xcca32f check_rtl /home/marxin/Programming/gcc/gcc/lra.c:2087 0xcceb1e lra(_IO_FILE*) /home/marxin/Programming/gcc/gcc/lra.c:2505 0xc85934 do_reload /home/marxin/Programming/gcc/gcc/ira.c:5827 0xc85934 execute /home/marxin/Programming/gcc/gcc/ira.c:6013 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2021-03-08 10:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-08 10:49 marxin at gcc dot gnu.org [this message] 2021-03-08 11:05 ` [Bug target/99461] " marxin at gcc dot gnu.org 2021-03-08 11:05 ` rguenth at gcc dot gnu.org 2021-03-08 11:10 ` marxin at gcc dot gnu.org 2021-03-08 18:58 ` vmakarov 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-99461-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: 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).