public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/116587] New: ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with custom flags
Date: Tue, 03 Sep 2024 18:12:59 +0000	[thread overview]
Message-ID: <bug-116587-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 116587
           Summary: ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1868
                    (unable to find a register to spill)
                    {*andndi3_doubleword_bmi} with custom flags
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

Created attachment 59045
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59045&action=edit
reduced testcase

This needs a lot of custom flags to reproduce; this looks similar to PR113048,
so it might be useful to someone having a look at that PR:

$ x86_64-pc-linux-gnu-gcc -O2 -fPIC -mstackrealign -mavx512f
-fharden-control-flow-redundancy -fno-omit-frame-pointer -m32 -mbmi
-fkeep-gc-roots-live testcase.c
testcase.c: In function 'h':
testcase.c:24:1: error: unable to find a register to spill
   24 | }
      | ^
testcase.c:24:1: error: this is the insn:
(insn 281 402 438 5 (parallel [
            (set (reg:DI 477 [360])
                (and:DI (not:DI (reg/v:DI 368 [orig:227 d ] [227]))
                    (mem:DI (plus:SI (reg:SI 443)
                            (reg:SI 444 [orig:158 ivtmp.69 ] [158])) [2
MEM[(long long unsigned int *)i_16(D) + ivtmp.69_139 * 1]+0 S8 A32])))
            (clobber (reg:CC 17 flags))
        ]) "testcase.c":11:8 806 {*andndi3_doubleword_bmi}
     (expr_list:REG_DEAD (reg:SI 443)
        (expr_list:REG_DEAD (reg:SI 444 [orig:158 ivtmp.69 ] [158])
            (expr_list:REG_DEAD (reg/v:DI 368 [orig:227 d ] [227])
                (expr_list:REG_UNUSED (reg:CC 17 flags)
                    (nil))))))
during RTL pass: reload
testcase.c:24:1: internal compiler error: in lra_split_hard_reg_for, at
lra-assigns.cc:1868
0x2be6f8e internal_error(char const*, ...)
        /repo/gcc-trunk/gcc/diagnostic-global-context.cc:492
0xe745d5 fancy_abort(char const*, int, char const*)
        /repo/gcc-trunk/gcc/diagnostic.cc:1658
0x830947 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /repo/gcc-trunk/gcc/rtl-error.cc:108
0x139bd2d lra_split_hard_reg_for()
        /repo/gcc-trunk/gcc/lra-assigns.cc:1868
0x13953c8 lra(_IO_FILE*, int)
        /repo/gcc-trunk/gcc/lra.cc:2521
0x134335f do_reload
        /repo/gcc-trunk/gcc/ira.cc:5976
0x134335f execute
        /repo/gcc-trunk/gcc/ira.cc:6164
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2024-09-03 18:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 18:12 zsojka at seznam dot cz [this message]
2024-09-03 18:27 ` [Bug rtl-optimization/116587] " ubizjak at gmail dot com
2024-09-04  8:01 ` ubizjak at gmail dot com
2024-09-04  9:33 ` ubizjak at gmail dot com
2024-09-04  9:35 ` [Bug target/116587] [14/15 Regression] " ubizjak at gmail dot com
2024-09-04  9:41 ` jakub at gcc dot gnu.org
2024-09-04 10:06 ` ubizjak at gmail dot com
2024-09-04 10:12 ` ubizjak at gmail dot com
2024-09-04 10:24 ` jakub at gcc dot gnu.org
2024-09-04 10:31 ` jakub at gcc dot gnu.org
2024-09-09  8:46 ` ubizjak at gmail dot com
2024-09-09  9:04 ` ubizjak at gmail dot com
2024-09-10  6:40 ` ubizjak at gmail dot com
2024-10-13 11:59 ` 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-116587-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).