public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rene at exactcode dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114466] New: mips: ICE during RTL pass: zero_call_used_regs
Date: Mon, 25 Mar 2024 13:07:41 +0000 [thread overview]
Message-ID: <bug-114466-4@http.gcc.gnu.org/bugzilla/> (raw)
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.
next reply other threads:[~2024-03-25 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:07 rene at exactcode dot de [this message]
2024-03-25 13:26 ` [Bug target/114466] " sjames at gcc dot gnu.org
2024-03-25 13:26 ` sjames at gcc dot gnu.org
2024-03-25 13:27 ` sjames at gcc dot gnu.org
2024-03-25 13:58 ` rene at exactcode dot de
2024-03-25 15:26 ` xry111 at gcc dot gnu.org
2024-03-25 16:30 ` rene at exactcode dot de
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-114466-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).