public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111488] New: ICE ion riscv gcc.dg/vect/vect-126.c
Date: Tue, 19 Sep 2023 21:47:32 +0000	[thread overview]
Message-ID: <bug-111488-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111488
           Summary: ICE ion riscv gcc.dg/vect/vect-126.c
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rdapp at gcc dot gnu.org
  Target Milestone: ---
            Target: riscv

I see an ICE in vect-126.c.  A small reproducer is:

int *a[1024], b[1024];

void
f1 (void)
{
  for (int i = 0; i < 1024; i++)
    {
      int *p = &b[0];
      a[i] = p + i;
    }
}

vect-126.c:18:1: internal compiler error: Segmentation fault
   18 | }
      | ^
0x111e61f crash_signal
        ../../gcc/toplev.cc:314
0xcfc91d mark_label_nuses
        ../../gcc/emit-rtl.cc:3755
0xcfc969 mark_label_nuses
        ../../gcc/emit-rtl.cc:3763
0xcfc969 mark_label_nuses
        ../../gcc/emit-rtl.cc:3763
0xcfc969 mark_label_nuses
        ../../gcc/emit-rtl.cc:3763

This happens after the splitter
(define_insn_and_split "*single_widen_fma<mode>".

At first glance it seems as if the insn sequence is corrupt as we're looking
into a <nil> value but I haven't checked further.  This is likely the same
error that prevents several SPECfp testcases to build.  Can investigate further
tomorrow.

             reply	other threads:[~2023-09-19 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 21:47 rdapp at gcc dot gnu.org [this message]
2023-09-19 21:50 ` [Bug target/111488] " rdapp at gcc dot gnu.org
2023-09-19 21:58 ` patrick at rivosinc dot com
2023-09-20  6:15 ` cvs-commit at gcc dot gnu.org
2023-11-22  6:08 ` rdapp 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-111488-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).