public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH] middle-end: move initialization of stack_limit_rtx [PR103163]
Date: Sat, 8 Jan 2022 21:24:09 -0700	[thread overview]
Message-ID: <ea5da06f-39aa-5e27-ce87-4e50233a72a8@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

This patch fixes the ICE I reported in PR103163.  We were initializing 
stack_limit_rtx before the register properties it depends on were 
getting set.  I moved it to the same function where stack_pointer_rtx, 
frame_pointer_rtx, etc are being initialized.

Besides nios2 where I observed it, this bug was also reported to affect 
powerpc.  Anybody want to check it there?  Otherwise, OK to check in?

-Sandra

[-- Attachment #2: pr103163.patch --]
[-- Type: text/x-patch, Size: 1930 bytes --]

commit bd91ec874339f9fd256b2d83de7159f6c11f0000
Author: Sandra Loosemore <sandra@codesourcery.com>
Date:   Sat Jan 8 19:59:26 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-08  Sandra Loosemore  <sandra@codesourcery.com>
    
    	PR middle-end/103163
    
    	gcc/
    	* emit-rtl.c (init_emit_regs): Initialize stack_limit_rtx here...
    	(init_emit_once): ...not here.

diff --git a/gcc/emit-rtl.c b/gcc/emit-rtl.c
index feeee16..76dbe42 100644
--- a/gcc/emit-rtl.c
+++ b/gcc/emit-rtl.c
@@ -6097,6 +6097,13 @@ init_emit_regs (void)
   if ((unsigned) PIC_OFFSET_TABLE_REGNUM != INVALID_REGNUM)
     pic_offset_table_rtx = gen_raw_REG (Pmode, PIC_OFFSET_TABLE_REGNUM);
 
+  /* Process stack-limiting command-line options.  */
+  if (opt_fstack_limit_symbol_arg != NULL)
+    stack_limit_rtx
+      = gen_rtx_SYMBOL_REF (Pmode, ggc_strdup (opt_fstack_limit_symbol_arg));
+  if (opt_fstack_limit_register_no >= 0)
+    stack_limit_rtx = gen_rtx_REG (Pmode, opt_fstack_limit_register_no);
+
   for (i = 0; i < (int) MAX_MACHINE_MODE; i++)
     {
       mode = (machine_mode) i;
@@ -6177,13 +6184,6 @@ init_emit_once (void)
 
   /* Create the unique rtx's for certain rtx codes and operand values.  */
 
-  /* Process stack-limiting command-line options.  */
-  if (opt_fstack_limit_symbol_arg != NULL)
-    stack_limit_rtx 
-      = gen_rtx_SYMBOL_REF (Pmode, ggc_strdup (opt_fstack_limit_symbol_arg));
-  if (opt_fstack_limit_register_no >= 0)
-    stack_limit_rtx = gen_rtx_REG (Pmode, opt_fstack_limit_register_no);
-
   /* Don't use gen_rtx_CONST_INT here since gen_rtx_CONST_INT in this case
      tries to use these variables.  */
   for (i = - MAX_SAVED_CONST_INT; i <= MAX_SAVED_CONST_INT; i++)

             reply	other threads:[~2022-01-09  4:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09  4:24 Sandra Loosemore [this message]
2022-01-17  3:14 ` Ping " Sandra Loosemore
2022-01-17  8:29   ` Richard Biener
2022-01-17 18:20     ` Sandra Loosemore
2022-01-18  8:43       ` Richard Biener

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=ea5da06f-39aa-5e27-ce87-4e50233a72a8@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gcc-patches@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).