public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/113029] New: sel-sched2 ICE in verify_target_availability
Date: Fri, 15 Dec 2023 06:44:21 +0000	[thread overview]
Message-ID: <bug-113029-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113029
           Summary: sel-sched2 ICE in verify_target_availability
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: linkw at gcc dot gnu.org
  Target Milestone: ---

Test case:

#include <altivec.h>
#define c(d, g) g, d
#define e(d, g) g, d
vector double f, n;
int m;
int k;
void j (vector double, double, double);
vector double combine (double, double);
vector double i (double, double);
vector double l (vector double, double);
vector double
o (vector double, double)
{
  vector double a;
  vector double b;
  p ("");
  j (f, c (1, 2));
  j (n, c (3, 4));
  b = i (3, 4);
  j (a, e (1, 2));
  j (b, e (3, 4));
  j (l (a, 5.0), e (5, 2));
  j (o (b, 6.0), e (3, 6));
  k = vec_extract (b, 1);
  j (combine (0, k), c (2, 4));
  m = vec_extract (b, 0);
  j (i (0, m), e (1, 3));
  i (0, vec_extract (b, 1));
}

Option: -std=c89 -O2 -mcpu=power10 -fselective-scheduling2

during RTL pass: sched2
test.c: In function ‘o’:
test.c:29:1: internal compiler error: in verify_target_availability, at
sel-sched.cc:1553
   29 | }
      | ^
0x10c54c43 verify_target_availability
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:1553
0x10c54c43 find_best_reg_for_expr
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:1667
0x10c54c43 fill_vec_av_set
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:3784
0x10c5555b fill_ready_list
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:4014
0x10c5555b find_best_expr
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:4374
0x10c5555b fill_insns
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:5535
0x10c5555b schedule_on_fences
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:7353
0x10c5555b sel_sched_region_2
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:7491
0x10c57b8b sel_sched_region_1
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:7533
0x10c59723 sel_sched_region(int)
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:7634
0x10c59723 sel_sched_region(int)
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:7619
0x10c59beb run_selective_scheduling()
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sel-sched.cc:7720
0x10c2e6ef rest_of_handle_sched2
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sched-rgn.cc:3748
0x10c2e6ef execute
        /home/gccbuild/gcc_trunk_git/gcc/gcc/sched-rgn.cc:3895

             reply	other threads:[~2023-12-15  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  6:44 linkw at gcc dot gnu.org [this message]
2023-12-15  6:50 ` [Bug rtl-optimization/113029] " pinskia at gcc dot gnu.org
2023-12-15  6:50 ` linkw at gcc dot gnu.org
2023-12-15  6:56 ` linkw 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-113029-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).