public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110372] New: [14 Regression] ICE: insn does not satisfy its constraints: {*movdi_internal} with -mno-sse2 Date: Thu, 22 Jun 2023 21:20:51 +0000 [thread overview] Message-ID: <bug-110372-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110372 Bug ID: 110372 Summary: [14 Regression] ICE: insn does not satisfy its constraints: {*movdi_internal} with -mno-sse2 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Created attachment 55389 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55389&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -O -mno-sse2 testcase.c testcase.c: In function 'foo0': testcase.c:11:1: error: insn does not satisfy its constraints: 11 | } | ^ (insn 36 3 41 2 (set (reg:DI 0 ax [123]) (reg:DI 20 xmm0 [orig:98 u ] [98])) "testcase.c":9:14 90 {*movdi_internal} (nil)) during RTL pass: reload testcase.c:11:1: internal compiler error: in extract_constrain_insn, at recog.cc:2692 0x7cc337 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /repo/gcc-trunk/gcc/rtl-error.cc:108 0x7cc3be _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /repo/gcc-trunk/gcc/rtl-error.cc:118 0x7bcc54 extract_constrain_insn(rtx_insn*) /repo/gcc-trunk/gcc/recog.cc:2692 0x12476b4 check_rtl /repo/gcc-trunk/gcc/lra.cc:2147 0x124be5b lra(_IO_FILE*) /repo/gcc-trunk/gcc/lra.cc:2565 0x11fb609 do_reload /repo/gcc-trunk/gcc/ira.cc:5967 0x11fb609 execute /repo/gcc-trunk/gcc/ira.cc:6153 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-2031-20230622101115-g2ac41866270-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r14-2031-20230622101115-g2ac41866270-checking-yes-rtl-df-extra-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.0 20230622 (experimental) (GCC)
next reply other threads:[~2023-06-22 21:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-22 21:20 zsojka at seznam dot cz [this message] 2023-06-23 2:20 ` [Bug target/110372] " pinskia at gcc dot gnu.org 2023-06-26 7:22 ` ubizjak at gmail dot com 2023-06-26 7:23 ` [Bug rtl-optimization/110372] " ubizjak at gmail dot com 2023-07-07 13:58 ` cvs-commit at gcc dot gnu.org 2023-07-15 6:28 ` pinskia 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-110372-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).