public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106030] New: ice in emit_move_insn, at expr.cc:4026
Date: Sun, 19 Jun 2022 16:02:38 +0000	[thread overview]
Message-ID: <bug-106030-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106030
           Summary: ice in emit_move_insn, at expr.cc:4026
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For this C code:

int safe_mul_func_int8_t_s_s_si2, g_7014, g_11941_l_12290;
char(safe_mul_func_uint8_t_u_u)(ui1, ui2) { return ui1 * ui2; }
void g_11941() {
  char __trans_tmp_1 =
      (safe_mul_func_uint8_t_u_u <= g_7014) * safe_mul_func_int8_t_s_s_si2;
  g_11941_l_12290 = safe_mul_func_uint8_t_u_u(2 != g_11941, __trans_tmp_1);
}

can be compiled like this:

$ /home/dcb/gcc/results/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/dcb/gcc/results/bin/gcc
COLLECT_LTO_WRAPPER=/home/dcb/gcc/results.20220617/libexec/gcc/arm-linux-gnueabihf/13.0.0/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../trunk/configure --prefix=/home/dcb/gcc/results.20220617
--disable-bootstrap --disable-multilib --disable-werror
--with-pkgversion=1d6044c250e3badf --enable-checking=yes
--enable-languages=c,c++ --with-cpu=cortex-a72 --with-fpu=neon-fp-armv8
--with-float=hard --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf
--target=arm-linux-gnueabihf
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20220617 (experimental) (1d6044c250e3badf) 
$ /home/dcb/gcc/results/bin/gcc -c  -w q.i
$

but switch on -O1 and this happens:

$ /home/dcb/gcc/results/bin/gcc -c  -w -O1 q.i 
during RTL pass: expand
q.i: In function 'g_11941':
q.i:6:19: internal compiler error: in emit_move_insn, at expr.cc:4026
    6 |   g_11941_l_12290 = safe_mul_func_uint8_t_u_u(2 != g_11941,
__trans_tmp_
1);
      |  
~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
0x551897 emit_move_insn(rtx_def*, rtx_def*)
        /home/dcb/gcc/working/gcc/../../trunk/gcc/expr.cc:4025
0x54608f expand_and(machine_mode, rtx_def*, rtx_def*, rtx_def*)
        /home/dcb/gcc/working/gcc/../../trunk/gcc/expmed.cc:5482

             reply	other threads:[~2022-06-19 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 16:02 dcb314 at hotmail dot com [this message]
2022-06-19 16:08 ` [Bug c/106030] " dcb314 at hotmail dot com
2022-06-20 12:11 ` [Bug target/106030] " jakub at gcc dot gnu.org
2022-06-20 12:11 ` [Bug middle-end/106030] " jakub at gcc dot gnu.org
2022-06-20 12:52 ` jakub at gcc dot gnu.org
2022-06-20 14:32 ` acoplan at gcc dot gnu.org
2022-06-20 14:34 ` [Bug middle-end/106030] [13 Regression] " jakub at gcc dot gnu.org
2022-06-20 14:34 ` jakub at gcc dot gnu.org
2022-06-20 14:49 ` dcb314 at hotmail dot com
2022-06-21  9:39 ` cvs-commit at gcc dot gnu.org
2022-06-28 15:38 ` cvs-commit at gcc dot gnu.org
2022-06-28 15:48 ` jakub at gcc dot gnu.org
2022-11-04  8:30 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:18 ` cvs-commit 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-106030-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).