public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yangyang305 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94574] New: aarch64: ICE during GIMPLE pass:ccp
Date: Mon, 13 Apr 2020 08:50:56 +0000	[thread overview]
Message-ID: <bug-94574-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94574
           Summary: aarch64: ICE during GIMPLE pass:ccp
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: yangyang305 at huawei dot com
  Target Milestone: ---

Hi, gcc-10 ICEs when compiling the following testcase with -O2
-msve-vector-bits=256 -march=armv8.2-a+sve

test case: gcc/testsuite/gcc.target/aarch64/sve/acle/general/deref_1.c
---
/* { dg-options "-O2" } */

#include <arm_sve.h>

uint64_t
f1 (int32_t *x, int32_t *y)
{
  union { uint64_t x; char c[8]; } u;
  svbool_t pg = svptrue_b32 ();
  *(svbool_t *)&u.c[0] = svcmpeq (pg, svld1 (pg, x), 0);
  *(svbool_t *)&u.c[4] = svcmpeq (pg, svld1 (pg, y), 1);
  return u.x;
}

typedef unsigned int v4si __attribute__((vector_size(16)));

/* The aliasing is somewhat dubious here, but it must compile.  */

v4si
f2 (void)
{
  v4si res;
  *(svuint32_t *) &res = svindex_u32 (0, 1);
  return res;
}
---
GCC version: 10.0.1 20200413 (experimental)

Result:
deref_1.c: In function ‘f2’:
deref_1.c:25:1: error: not allowed type combination in ‘bit_insert_expr’
   25 | }
      | ^
v4si
vector(8) unsigned int
res_9 = BIT_INSERT_EXPR <res_8(D), _7, 0>;
during GIMPLE pass: ccp
deref_1.c:25:1: internal compiler error: verify_gimple failed
0xcfc9b7 verify_gimple_in_cfg(function*, bool)
        ../.././gcc/tree-cfg.c:5462
0xbc534b execute_function_todo
        ../.././gcc/passes.c:1985
0xbc622b do_per_function
        ../.././gcc/passes.c:1640
0xbc622b execute_todo
        ../.././gcc/passes.c:2039
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-13  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  8:50 yangyang305 at huawei dot com [this message]
2020-04-13  9:24 ` [Bug tree-optimization/94574] " yangyang305 at huawei dot com
2020-04-13 10:00 ` yangyang305 at huawei dot com
2020-04-14  6:37 ` marxin at gcc dot gnu.org
2020-04-14  6:37 ` marxin at gcc dot gnu.org
2020-04-14 14:01 ` cvs-commit at gcc dot gnu.org
2020-04-14 14:02 ` 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-94574-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).