public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112686] [14 Regression] ICE: in gen_reg_rtx, at emit-rtl.cc:1176 with -fsplit-stack -mcmodel=large
Date: Fri, 24 Nov 2023 12:53:34 +0000 [thread overview]
Message-ID: <bug-112686-4-EniLVtlBjz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112686-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112686
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
Status|NEW |ASSIGNED
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc
index 7b922857d80..50e8826dbe5 100644
--- a/gcc/config/i386/i386.cc
+++ b/gcc/config/i386/i386.cc
@@ -10503,7 +10503,7 @@ ix86_expand_split_stack_prologue (void)
fn = copy_to_suggested_reg (x, reg11, Pmode);
}
else
- fn = split_stack_fn_large;
+ fn = copy_to_suggested_reg (split_stack_fn_large, reg11, Pmode);
/* When using the large model we need to load the address
into a register, and we've run out of registers. So we
next prev parent reply other threads:[~2023-11-24 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 21:30 [Bug target/112686] New: " zsojka at seznam dot cz
2023-11-23 21:37 ` [Bug target/112686] " pinskia at gcc dot gnu.org
2023-11-24 11:23 ` jakub at gcc dot gnu.org
2023-11-24 12:53 ` ubizjak at gmail dot com [this message]
2023-11-24 16:32 ` cvs-commit at gcc dot gnu.org
2023-11-24 16:34 ` ubizjak at gmail dot com
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-112686-4-EniLVtlBjz@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).