public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113193] [SH] ICE in gen_reg_rtx, at emit-rtl.cc:1177 with -mfcsa -funsafe-math-operations
Date: Fri, 05 Jan 2024 05:39:50 +0000	[thread overview]
Message-ID: <bug-113193-4-W3VFwV6W0O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113193-4@http.gcc.gnu.org/bugzilla/>

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

Oleg Endo <olegendo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |13.2.1
            Version|14.0                        |13.0
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |ra
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-01-05

--- Comment #1 from Oleg Endo <olegendo at gcc dot gnu.org> ---
I was able to reproduce the bug with the following compiler options on 13
branch:

-x c++ -std=c++17 -O3 -m4-single -ml -mfsca -mfsrra -funsafe-math-optimizations


combined.cpp: In function 'void transform(const model_transform&, const vec3*,
int, float*)':
combined.cpp:574:1: internal compiler error: in gen_reg_rtx, at
emit-rtl.cc:1171
0x61da53 gen_reg_rtx(machine_mode)
        ../../gcc/gcc/emit-rtl.cc:1171
0x9e8cc1 copy_to_reg(rtx_def*)
        ../../gcc/gcc/explow.cc:622
0x9d7727 operand_subword_force(rtx_def*, poly_int<1u, unsigned long>,
machine_mode)
        ../../gcc/gcc/emit-rtl.cc:1812
0xa0eddc emit_move_multi_word
        ../../gcc/gcc/expr.cc:4129
0xa12bdb gen_move_insn(rtx_def*, rtx_def*)
        ../../gcc/gcc/expr.cc:4359
0xccfcda gen_reload
        ../../gcc/gcc/reload1.cc:8614
0xcd8956 emit_output_reload_insns
        ../../gcc/gcc/reload1.cc:7667
0xcd8956 do_output_reload
        ../../gcc/gcc/reload1.cc:7939
0xcd8956 emit_reload_insns
        ../../gcc/gcc/reload1.cc:8003
0xcd8956 reload_as_needed
        ../../gcc/gcc/reload1.cc:4543
0xcdc460 reload(rtx_insn*, int)
        ../../gcc/gcc/reload1.cc:1047
0xb78004 do_reload
        ../../gcc/gcc/ira.cc:5975
0xb78004 execute
        ../../gcc/gcc/ira.cc:6149


With added -mlra:

ombined.cpp: In function 'void transform(const model_transform&, const vec3*,
int, float*)':
combined.cpp:574:1: internal compiler error: maximum number of generated reload
insns per insn achieved (90)
0xbd0699 lra_constraints(bool)
        ../../gcc/gcc/lra-constraints.cc:5258
0xbbc182 lra(_IO_FILE*)
        ../../gcc/gcc/lra.cc:2375
0xb77999 do_reload
        ../../gcc/gcc/ira.cc:5963
0xb77999 execute
        ../../gcc/gcc/ira.cc:6149

      reply	other threads:[~2024-01-05  5:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02  1:52 [Bug target/113193] New: " zack+gcc at buhman dot org
2024-01-05  5:39 ` olegendo at gcc dot gnu.org [this message]

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-113193-4-W3VFwV6W0O@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).