public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103163] [12 Regression] stack_limit_rtx is created too early causing nregs field on REG to be zero (gcc.target/nios2/nios2-stack-check-1.c and gcc.target/powerpc/stack-limit.c)
Date: Tue, 18 Jan 2022 17:29:12 +0000 [thread overview]
Message-ID: <bug-103163-4-59m5NVuZTC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103163-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103163
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>:
https://gcc.gnu.org/g:3a0837b8fb96f50f2e60222ce289cc2542bbb477
commit r12-6693-g3a0837b8fb96f50f2e60222ce289cc2542bbb477
Author: Sandra Loosemore <sandra@codesourcery.com>
Date: Tue Jan 18 09:27:36 2022 -0800
middle-end: move initialization of stack_limit_rtx [PR103163]
stack_limit_rtx was being initialized before init_reg_modes_target (),
resulting in the REG expression being created incorrectly and an ICE
later in compilation.
2022-01-18 Sandra Loosemore <sandra@codesourcery.com>
PR middle-end/103163
gcc/
* emit-rtl.cc (init_emit_regs): Initialize stack_limit_rtx here...
(init_emit_once): ...not here.
next prev parent reply other threads:[~2022-01-18 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 2:48 [Bug other/103163] New: stack_limit_rtx is created too early sandra at gcc dot gnu.org
2021-11-17 7:36 ` [Bug middle-end/103163] " pinskia at gcc dot gnu.org
2021-11-17 7:40 ` [Bug middle-end/103163] [12 Regression] " pinskia at gcc dot gnu.org
2021-11-17 7:40 ` pinskia at gcc dot gnu.org
2022-01-17 12:59 ` [Bug middle-end/103163] [12 Regression] stack_limit_rtx is created too early causing nregs field on REG to be zero (gcc.target/nios2/nios2-stack-check-1.c and gcc.target/powerpc/stack-limit.c) rguenth at gcc dot gnu.org
2022-01-17 17:37 ` pinskia at gcc dot gnu.org
2022-01-18 17:29 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-18 17:32 ` sandra 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-103163-4-59m5NVuZTC@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).