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/97140] New: [10/11 Regression] ICE in error: unable to generate reloads for since r10-400-gecfdb16c54ad06ac Date: Mon, 21 Sep 2020 10:36:37 +0000 [thread overview] Message-ID: <bug-97140-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97140 Bug ID: 97140 Summary: [10/11 Regression] ICE in error: unable to generate reloads for since r10-400-gecfdb16c54ad06ac Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: hjl.tools at gmail dot com Target Milestone: --- The following is causing ICE: $ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr48084-2.c -mno-mmx -c /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr48084-2.c: In function '_mm_maskmove_si64': /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr48084-2.c:10:1: error: unable to generate reloads for: 10 | } | ^ (insn 11 10 14 2 (set (mem:V8QI (reg/f:DI 84) [0 S8 A8]) (unspec:V8QI [ (reg:V8QI 83 [ _2 ]) (reg:V8QI 82 [ _1 ]) (mem:V8QI (reg/f:DI 84) [0 S8 A8]) ] UNSPEC_MASKMOV)) "/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr48084-2.c":9:5 1391 {*mmx_maskmovq} (expr_list:REG_DEAD (reg/f:DI 84) (expr_list:REG_DEAD (reg:V8QI 83 [ _2 ]) (expr_list:REG_DEAD (reg:V8QI 82 [ _1 ]) (nil))))) during RTL pass: reload /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr48084-2.c:10:1: internal compiler error: in curr_insn_transform, at lra-constraints.c:4074 0x6baeff _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /home/marxin/Programming/gcc/gcc/rtl-error.c:108 0x699f26 curr_insn_transform /home/marxin/Programming/gcc/gcc/lra-constraints.c:4074 0xc1e676 lra_constraints(bool) /home/marxin/Programming/gcc/gcc/lra-constraints.c:5100 0xc0b7bc lra(_IO_FILE*) /home/marxin/Programming/gcc/gcc/lra.c:2415 0xbc6c81 do_reload /home/marxin/Programming/gcc/gcc/ira.c:5529 0xbc6c81 execute /home/marxin/Programming/gcc/gcc/ira.c:5715 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:[~2020-09-21 10:36 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 10:36 marxin at gcc dot gnu.org [this message] 2020-09-21 11:30 ` [Bug target/97140] " rguenth at gcc dot gnu.org 2020-09-21 12:55 ` hjl.tools at gmail dot com 2020-09-21 13:12 ` hjl.tools at gmail dot com 2020-10-12 11:50 ` rguenth at gcc dot gnu.org 2020-10-12 11:59 ` hjl.tools at gmail dot com 2020-11-02 21:59 ` cvs-commit at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-04-21 13:11 ` [Bug target/97140] [10/11/12 " asolokha at gmx dot com 2022-06-28 10:41 ` [Bug target/97140] [10/11/12/13 " jakub at gcc dot gnu.org 2023-07-07 10:38 ` [Bug target/97140] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-03-10 23:03 ` law 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-97140-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).