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 target/105334] New: [12 Regression] ICE in curr_insn_transform,  at lra-constraints.cc:4168 (error: unable to generate reloads)
Date: Thu, 21 Apr 2022 13:07:03 +0000	[thread overview]
Message-ID: <bug-105334-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105334
           Summary: [12 Regression] ICE in curr_insn_transform, at
                    lra-constraints.cc:4168 (error: unable to generate
                    reloads)
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: accepts-invalid, ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
                CC: bergner at gcc dot gnu.org, linkw at gcc dot gnu.org,
                    segher at gcc dot gnu.org
  Target Milestone: ---
            Target: powerpc-*-linux-gnu

gcc 12.0.1 20220417 snapshot (g:000c1b89d259fadb466e1f2e63c79da45fd17372) ICEs
when compiling the following testcase, reduced from
gcc/testsuite/gcc.target/powerpc/pack02.c, w/ -mcpu=401:

long double
foo (void)
{
  return __builtin_pack_longdouble (1.0, 1.0);
}

% powerpc-e300c3-linux-gnu-gcc-12.0.1 -mcpu=401 -c eqozx4uz.c
eqozx4uz.c: In function 'foo':
eqozx4uz.c:5:1: error: unable to generate reloads for:
    5 | }
      | ^
(insn 7 6 10 2 (set (reg:TF 117 [ _1 ])
        (unspec:TF [
                (reg:DF 119)
                (reg:DF 120)
            ] UNSPEC_PACK_128BIT)) "eqozx4uz.c":4:10 1070 {packtf}
     (expr_list:REG_DEAD (reg:DF 120)
        (expr_list:REG_DEAD (reg:DF 119)
            (nil))))
during RTL pass: reload
eqozx4uz.c:5:1: internal compiler error: in curr_insn_transform, at
lra-constraints.cc:4168
0x690c51 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/rtl-error.cc:108
0x66b2b7 curr_insn_transform
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/lra-constraints.cc:4168
0xc9a615 lra_constraints(bool)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/lra-constraints.cc:5203
0xc848ba lra(_IO_FILE*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/lra.cc:2375
0xc3b989 do_reload
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/ira.cc:5940
0xc3b989 execute
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/ira.cc:6126

             reply	other threads:[~2022-04-21 13:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 13:07 asolokha at gmx dot com [this message]
2022-04-21 18:02 ` [Bug target/105334] " segher at gcc dot gnu.org
2022-04-21 18:05 ` segher at gcc dot gnu.org
2022-04-21 22:54 ` segher at gcc dot gnu.org
2022-04-21 23:50 ` segher at gcc dot gnu.org
2022-04-22  2:33 ` linkw at gcc dot gnu.org
2022-04-22  5:58 ` rguenth at gcc dot gnu.org
2022-04-22 19:29 ` cvs-commit at gcc dot gnu.org
2022-04-22 19:54 ` segher at gcc dot gnu.org
2022-04-26  8:46 ` [Bug target/105334] " jakub at gcc dot gnu.org
2022-04-28  3:35 ` cvs-commit at gcc dot gnu.org
2022-04-28  3:39 ` 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-105334-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).