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 tree-optimization/107326] New: [13 Regression] ICE: verify_gimple failed (error: type mismatch in binary expression)
Date: Thu, 20 Oct 2022 03:19:10 +0000	[thread overview]
Message-ID: <bug-107326-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107326
           Summary: [13 Regression] ICE: verify_gimple failed (error: type
                    mismatch in binary expression)
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---
            Target: aarch64-linux-gnu

gcc 13.0.0 20221016 snapshot (g:6366e3e8847af98d4728d55951534769d034d02a) ICEs
when compiling the following testcase w/ -O2 -fallow-store-data-races
-fvect-cost-model=dynamic:

struct Gsymtab {
  unsigned int : 8;
  unsigned int visited_somewhere : 1;
};

extern struct Gsymtab glob_symtab[];

int
visit_children (int i)
{
  int numvisited = 0;

  while (i < 1)
    {
      if (glob_symtab[i].visited_somewhere)
        ++numvisited;

      ++i;
    }

  return numvisited;
}

% aarch64-linux-gnu-gcc-13 -O2 -fallow-store-data-races
-fvect-cost-model=dynamic -c cjjq0il5.ccjjq0il5.c: In function
'visit_children':
cjjq0il5.c:9:1: error: type mismatch in binary expression
    9 | visit_children (int i)
      | ^~~~~~~~~~~~~~
vector(4) short unsigned int

vector(4) int

vector(4) int

vect_patt_8.16_64 = vect_patt_3.15_62 & { 256, 256, 256, 256 };
cjjq0il5.c:9:1: error: type mismatch in binary expression
vector(4) int

vector(4) int

vector(4) short unsigned int

vect__23.18_66 = vect_numvisited_12.10_51 + vect_patt_24.17_65;
during GIMPLE pass: vect
cjjq0il5.c:9:1: internal compiler error: verify_gimple failed
0xf81d0d verify_gimple_in_cfg(function*, bool)
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/tree-cfg.cc:5649
0xe3def7 execute_function_todo
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/passes.cc:2091
0xe3e42e execute_todo
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/passes.cc:2145

             reply	other threads:[~2022-10-20  3:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  3:19 asolokha at gmx dot com [this message]
2022-10-20  9:24 ` [Bug tree-optimization/107326] " rguenth at gcc dot gnu.org
2022-10-20  9:25 ` [Bug tree-optimization/107326] [13 Regression] ICE: verify_gimple failed (error: type mismatch in binary expression) since r13-3219-g25413fdb2ac249 marxin at gcc dot gnu.org
2022-10-20  9:25 ` marxin at gcc dot gnu.org
2022-10-20 10:19 ` avieira at gcc dot gnu.org
2022-10-20 14:55 ` cvs-commit at gcc dot gnu.org
2022-11-13 10:11 ` ramana at gcc dot gnu.org
2022-11-14 16:56 ` avieira at gcc dot gnu.org
2022-11-15  0:32 ` asolokha at gmx dot com
2022-11-15  9:58 ` avieira 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-107326-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).