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/94614] New: [10 Regression] ICE in emit_move_multi_word,  at expr.c:3716 since r10-416-g1bf2a0b90f2457f6d9301535560eb5e05978261b
Date: Thu, 16 Apr 2020 07:21:14 +0000	[thread overview]
Message-ID: <bug-94614-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94614

            Bug ID: 94614
           Summary: [10 Regression] ICE in emit_move_multi_word, at
                    expr.c:3716 since
                    r10-416-g1bf2a0b90f2457f6d9301535560eb5e05978261b
           Product: gcc
           Version: 10.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: rguenth at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-linux-gnu
            Target: arm-none-eabi-gcc,riscv64-linux-gnu

I see the following ICE

$ ./gcc/xgcc -Bgcc /home/marxin/Programming/gcc2/gcc/testsuite/gcc.dg/pr94574.c
-c -Og
during RTL pass: expand
/home/marxin/Programming/gcc2/gcc/testsuite/gcc.dg/pr94574.c: In function
‘foo’:
/home/marxin/Programming/gcc2/gcc/testsuite/gcc.dg/pr94574.c:13:18: internal
compiler error: in emit_move_multi_word, at expr.c:3716
   13 |   *(v4si *) &res = v;
      |   ~~~~~~~~~~~~~~~^~~
0xca66a2 emit_move_multi_word
        /home/marxin/Programming/gcc2/gcc/expr.c:3716
0xca6a56 emit_move_insn_1(rtx_def*, rtx_def*)
        /home/marxin/Programming/gcc2/gcc/expr.c:3791
0xca6cb1 emit_move_insn(rtx_def*, rtx_def*)
        /home/marxin/Programming/gcc2/gcc/expr.c:3850
0xc81b1a store_bit_field_1
        /home/marxin/Programming/gcc2/gcc/expmed.c:806
0xc835fa 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/marxin/Programming/gcc2/gcc/expmed.c:1172
0xcb408a store_field
        /home/marxin/Programming/gcc2/gcc/expr.c:7192
0xcabafc expand_assignment(tree_node*, tree_node*, bool)
        /home/marxin/Programming/gcc2/gcc/expr.c:5369
0xb25d0e expand_gimple_stmt_1
        /home/marxin/Programming/gcc2/gcc/cfgexpand.c:3749
0xb26107 expand_gimple_stmt
        /home/marxin/Programming/gcc2/gcc/cfgexpand.c:3847
0xb2e1d1 expand_gimple_basic_block
        /home/marxin/Programming/gcc2/gcc/cfgexpand.c:5887
0xb2fc15 execute
        /home/marxin/Programming/gcc2/gcc/cfgexpand.c:6542
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.

             reply	other threads:[~2020-04-16  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  7:21 marxin at gcc dot gnu.org [this message]
2020-04-16  7:21 ` [Bug target/94614] " marxin at gcc dot gnu.org
2020-04-16  7:28 ` rguenth at gcc dot gnu.org
2020-04-16  7:36 ` marxin at gcc dot gnu.org
2020-04-16  7:39 ` [Bug target/94614] ICE in emit_move_multi_word, at expr.c:3716 marxin at gcc dot gnu.org
2020-04-16  7:40 ` rguenth at gcc dot gnu.org
2020-04-16  7:53 ` rguenth at gcc dot gnu.org
2020-04-16 10:55 ` cvs-commit at gcc dot gnu.org
2020-04-16 10:55 ` 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-94614-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: link
Be 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).