public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sirl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110496] New: ICE: tree check: expected none of vector_type, have vector_type in find_bswap_or_nop_1, at gimple-ssa-store-merging.cc:654
Date: Fri, 30 Jun 2023 09:21:25 +0000	[thread overview]
Message-ID: <bug-110496-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110496
           Summary: ICE: tree check: expected none of vector_type, have
                    vector_type in find_bswap_or_nop_1, at
                    gimple-ssa-store-merging.cc:654
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sirl at gcc dot gnu.org
  Target Milestone: ---

This testcase (reduced with cvise):

long contents, f_num;
int decide();
int f_MV0__x;
void f() {
  unsigned char *rptr;
  unsigned char valbuf[6];
  rptr = (unsigned char *)contents;
  if (decide())
    do {
      __builtin_memcpy(valbuf, &f_MV0__x, sizeof(int));
      (&valbuf[0])[4] = (&valbuf[0])[5] = 0;
    } while (0);
  else {
    int MV0__x = f_num;
    __builtin_memcpy(valbuf, &MV0__x, sizeof(int));
    (&valbuf[0])[4] = (&valbuf[0])[5] = 0;
  }
  rptr[1] = valbuf[4];
  rptr[2] = valbuf[5];
  rptr[4] = valbuf[1];
  rptr[5] = valbuf[2];
  __builtin_memset(valbuf, 0, 8);
}

ICEs with gcc@r14-2190:

during GIMPLE pass: store-merging
testcase.c: In function 'f':
testcase.c:4:6: internal compiler error: tree check: expected none of
vector_type, have vector_type in find_bswap_or_nop_1, at
gimple-ssa-store-merging.cc:654
    4 | void f() {
      |      ^
0x921335 tree_not_check_failed(tree_node const*, char const*, int, char const*,
...)
        ../../gcc/tree.cc:8936
0x11175d8 tree_not_check(tree_node*, char const*, int, char const*, tree_code)
        ../../gcc/tree.h:3581
0x11175d8 find_bswap_or_nop_1
        ../../gcc/gimple-ssa-store-merging.cc:654
0x17c6758 process_store
        ../../gcc/gimple-ssa-store-merging.cc:5269
0x17c6758 execute
        ../../gcc/gimple-ssa-store-merging.cc:5557

             reply	other threads:[~2023-06-30  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  9:21 sirl at gcc dot gnu.org [this message]
2023-06-30  9:51 ` [Bug tree-optimization/110496] " rguenth at gcc dot gnu.org
2023-06-30 10:15 ` sirl at gcc dot gnu.org
2023-06-30 10:59 ` cvs-commit at gcc dot gnu.org
2023-06-30 11:00 ` 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-110496-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).