public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com>
To: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PING][PATCH] ira: update allocated_hardreg_p[] in improve_allocation() [PR110254]
Date: Wed, 2 Aug 2023 09:23:53 -0400	[thread overview]
Message-ID: <42cb722f-45ed-eec9-d15d-84c2f4a7a7d4@redhat.com> (raw)
In-Reply-To: <2ade3beb-adb6-a911-0600-c1e80b12d280@linux.vnet.ibm.com>


On 8/1/23 01:20, Surya Kumari Jangala wrote:
> Ping
Sorry for delay with the answer. I was on vacation.
> On 21/07/23 3:43 pm, Surya Kumari Jangala via Gcc-patches wrote:
>> The improve_allocation() routine does not update the
>> allocated_hardreg_p[] array after an allocno is assigned a register.
>>
>> If the register chosen in improve_allocation() is one that already has
>> been assigned to a conflicting allocno, then allocated_hardreg_p[]
>> already has the corresponding bit set to TRUE, so nothing needs to be
>> done.
>>
>> But improve_allocation() can also choose a register that has not been
>> assigned to a conflicting allocno, and also has not been assigned to any
>> other allocno. In this case, allocated_hardreg_p[] has to be updated.
The patch is OK for me.  Thank you for finding and fixing this issue.
>> 2023-07-21  Surya Kumari Jangala  <jskumari@linux.ibm.com>
>>
>> gcc/
>> 	PR rtl-optimization/PR110254
>> 	* ira-color.cc (improve_allocation): Update array

I guess you missed the next line in the changelog.  I suspect it should 
be "Update array allocated_hard_reg_p."

Please, fix it before committing the patch.

>> ---
>>
>> diff --git a/gcc/ira-color.cc b/gcc/ira-color.cc
>> index 1fb2958bddd..5807d6d26f6 100644
>> --- a/gcc/ira-color.cc
>> +++ b/gcc/ira-color.cc
>> @@ -3340,6 +3340,10 @@ improve_allocation (void)
>>   	}
>>         /* Assign the best chosen hard register to A.  */
>>         ALLOCNO_HARD_REGNO (a) = best;
>> +
>> +      for (j = nregs - 1; j >= 0; j--)
>> +	allocated_hardreg_p[best + j] = true;
>> +
>>         if (internal_flag_ira_verbose > 2 && ira_dump_file != NULL)
>>   	fprintf (ira_dump_file, "Assigning %d to a%dr%d\n",
>>   		 best, ALLOCNO_NUM (a), ALLOCNO_REGNO (a));


  reply	other threads:[~2023-08-02 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 10:13 [PATCH] " Surya Kumari Jangala
2023-08-01  5:20 ` [PING][PATCH] " Surya Kumari Jangala
2023-08-02 13:23   ` Vladimir Makarov [this message]
2023-08-18 16:51     ` Peter Bergner

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=42cb722f-45ed-eec9-d15d-84c2f4a7a7d4@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=bergner@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jskumari@linux.vnet.ibm.com \
    /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).