public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100106] New: [10/11 Regression] ICE in gen_movdi, at config/arm/arm.md:6187 since r10-2840-g70cdb21e Date: Thu, 15 Apr 2021 21:06:00 +0000 [thread overview] Message-ID: <bug-100106-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100106 Bug ID: 100106 Summary: [10/11 Regression] ICE in gen_movdi, at config/arm/arm.md:6187 since r10-2840-g70cdb21e Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- The following fails: $ cat test.c union a { float _Complex b; long long c; }; void g(union a); void e() { union a f = {1.0f}; g(f); } $ gcc/xgcc -B gcc test.c -c -O during RTL pass: expand test.c: In function ‘e’: test.c:9:11: internal compiler error: in gen_movdi, at config/arm/arm.md:6187 9 | union a f = {1.0f}; | ^ 0x1de9e64 gen_movdi(rtx_def*, rtx_def*) /home/alecop01/toolchain/src/gcc/gcc/config/arm/arm.md:6187 0xdb9086 rtx_insn* insn_gen_fn::operator()<rtx_def*, rtx_def*>(rtx_def*, rtx_def*) const /home/alecop01/toolchain/src/gcc/gcc/recog.h:407 0xd8ff58 emit_move_insn_1(rtx_def*, rtx_def*) /home/alecop01/toolchain/src/gcc/gcc/expr.c:3766 0xd909ca emit_move_insn(rtx_def*, rtx_def*) /home/alecop01/toolchain/src/gcc/gcc/expr.c:3936 0xd69cbb store_bit_field_1 /home/alecop01/toolchain/src/gcc/gcc/expmed.c:804 0xd6b8bb store_bit_field(rtx_def*, poly_int<1u, unsigned long>, poly_int<1u, unsigned long>, poly_int<1u, unsigned long>, poly_int<1u, unsigned long>, machine_mode, rtx_def*, bool) /home/alecop01/toolchain/src/gcc/gcc/expmed.c:1183 0xd9eaef store_field /home/alecop01/toolchain/src/gcc/gcc/expr.c:7353 0xd95ddf expand_assignment(tree_node*, tree_node*, bool) /home/alecop01/toolchain/src/gcc/gcc/expr.c:5482 0xbf2c4e expand_gimple_stmt_1 /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.c:3910 0xbf303d expand_gimple_stmt /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.c:4008 0xbfbaa3 expand_gimple_basic_block /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.c:6045 0xbfd954 execute /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.c:6729 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. Started with r10-2840-g70cdb21e579191fe9f0f1d45e328908e59c0179e.
next reply other threads:[~2021-04-15 21:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 21:06 acoplan at gcc dot gnu.org [this message] 2021-04-15 21:06 ` [Bug target/100106] " acoplan at gcc dot gnu.org 2021-04-16 7:09 ` rguenth at gcc dot gnu.org 2021-04-16 7:13 ` rguenth at gcc dot gnu.org 2021-04-20 6:00 ` bernd.edlinger at hotmail dot de 2021-04-27 15:48 ` [Bug target/100106] [10/11/12 " cvs-commit at gcc dot gnu.org 2021-04-27 15:51 ` [Bug target/100106] [10/11 " edlinger at gcc dot gnu.org 2021-07-19 11:59 ` rguenth at gcc dot gnu.org 2022-04-07 10:39 ` cvs-commit at gcc dot gnu.org 2022-04-08 10:20 ` [Bug target/100106] [10 " rearnsha at gcc dot gnu.org 2022-06-28 10:44 ` jakub at gcc dot gnu.org 2023-05-25 2:46 ` cvs-commit at gcc dot gnu.org 2023-07-07 9:35 ` rguenth 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-100106-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).