[Bug target/114466] New: mips: ICE during RTL pass: zero_call_used_regs

[Bug target/114466] New: mips: ICE during RTL pass: zero_call_used_regs

[rene at exactcode dot de]

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

            Bug ID: 114466
           Summary: mips: ICE during RTL pass: zero_call_used_regs
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rene at exactcode dot de
  Target Milestone: ---

Compiling the latest openssh-9.7p1 (and openssh-9.6p1) for mips-linux or
mips64n32 linux causes and internal compiler error: Segmentation fault:

uring RTL pass: zero_call_used_regs
misc.c: In function 'bandwidth_limit':
misc.c:1807:1: internal compiler error: Segmentation fault
 1807 | }
      | ^
0x128fff5 internal_error(char const*, ...)
        ???:0
0x863ad0 emit_move_insn(rtx_def*, rtx_def*)
        ???:0
0xac9967 default_zero_call_used_regs(HARD_REG_SET)
        ???:0
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.

at least 14-20240324 and 13-20240224 are affected. I would expect at leaste
13.2 as well.

[Bug target/114466] mips: ICE during RTL pass: zero_call_used_regs

[sjames at gcc dot gnu.org]

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

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sjames at gcc dot gnu.org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #1 from Sam James <sjames at gcc dot gnu.org> ---
Dupe.

*** This bug has been marked as a duplicate of bug 110934 ***

[Bug target/114466] mips: ICE during RTL pass: zero_call_used_regs

[sjames at gcc dot gnu.org]

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

--- Comment #2 from Sam James <sjames at gcc dot gnu.org> ---
Also:
>Please submit a full bug report, with preprocessed source (by using -freport-bug).

But no need here.

[Bug target/114466] mips: ICE during RTL pass: zero_call_used_regs

[sjames at gcc dot gnu.org]

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

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|DUPLICATE                   |---
             Status|RESOLVED                    |UNCONFIRMED

--- Comment #3 from Sam James <sjames at gcc dot gnu.org> ---
Oh, no, it isn't. Yeah, preprocessed source please.

[Bug target/114466] mips: ICE during RTL pass: zero_call_used_regs

[rene at exactcode dot de]

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

--- Comment #4 from René Rebe <rene at exactcode dot de> ---
Created attachment 57809
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57809&action=edit
preprocessed source from -freport-bug

preprocessed source from -freport-bug

[Bug target/114466] mips: ICE during RTL pass: zero_call_used_regs

[xry111 at gcc dot gnu.org]

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #5 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
-fzero-call-used-regs=all is just completely broken on mips as at now.  Please
don't use it for mips.

[Bug target/114466] mips: ICE during RTL pass: zero_call_used_regs

[rene at exactcode dot de]

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

--- Comment #6 from René Rebe <rene at exactcode dot de> ---
ok - good to know. I guess someone should tell the openssh developers and maybe
gcc should error out with a warning. Actually if gcc would error out it would
signal openssl's configure not to automatically try to use it, ...