public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101505] New: [10/11/12 Regression] ICE: verify_gimple failed (error: incompatible types in 'PHI' argument 0)
Date: Mon, 19 Jul 2021 07:35:10 +0000	[thread overview]
Message-ID: <bug-101505-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101505
           Summary: [10/11/12 Regression] ICE: verify_gimple failed
                    (error: incompatible types in 'PHI' argument 0)
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---
            Target: aarch64-linux-gnu

gcc-12.0.0-alpha20210718 snapshot (g:6ae8aac19cdbdbd96d90f86e4d8505fe121bdf06)
ICEs when compiling the following testcase w/ -O1:

int n2;

__attribute__ ((simd)) char
w7 (void)
{
  short int xb = n2;
  int qp;

  for (qp = 0; qp < 2; ++qp)
    xb = xb < 1;

  return xb;
}

% aarch64-linux-gnu-gcc-12.0.0 -O1 -c zo3xlee1.c
zo3xlee1.c: In function 'w7.simdclone.0':
zo3xlee1.c:4:1: error: incompatible types in 'PHI' argument 0
    4 | w7 (void)
      | ^~
vector(8) unsigned char

vector(8) <signed-boolean:16>

vect__18.21_29 = PHI <mask__4.19_25(4)>
during GIMPLE pass: vect
zo3xlee1.c:4:1: internal compiler error: verify_gimple failed
0xf62af7 verify_gimple_in_cfg(function*, bool)
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210718/work/gcc-12-20210718/gcc/tree-cfg.c:5536
0xe291ce execute_function_todo
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210718/work/gcc-12-20210718/gcc/passes.c:2042
0xe298d1 do_per_function
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210718/work/gcc-12-20210718/gcc/passes.c:1687
0xe298d1 execute_todo
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210718/work/gcc-12-20210718/gcc/passes.c:2096

             reply	other threads:[~2021-07-19  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  7:35 asolokha at gmx dot com [this message]
2021-07-19  7:45 ` [Bug target/101505] " rguenth at gcc dot gnu.org
2021-07-19 11:26 ` rguenth at gcc dot gnu.org
2021-07-19 11:26 ` rguenth at gcc dot gnu.org
2021-07-19 12:21 ` cvs-commit at gcc dot gnu.org
2021-07-19 12:22 ` [Bug target/101505] [10/11 " rguenth at gcc dot gnu.org
2021-08-04 20:49 ` dcb314 at hotmail dot com
2021-08-04 21:13 ` dcb314 at hotmail dot com
2021-08-05  8:16 ` rguenth at gcc dot gnu.org
2021-08-05 18:31 ` dcb314 at hotmail dot com
2021-08-06  9:43 ` cvs-commit at gcc dot gnu.org
2021-09-06  9:10 ` [Bug target/101505] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:45 ` jakub at gcc dot gnu.org
2023-07-07  9:44 ` 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-101505-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).