From: Vladimir Makarov <vmakarov@redhat.com>
To: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] ira: Consider save/restore costs of callee-save registers [PR110071]
Date: Fri, 15 Sep 2023 10:48:08 -0400 [thread overview]
Message-ID: <695dda93-85a8-450a-0e6a-58da24884c06@redhat.com> (raw)
In-Reply-To: <d4eb2a39-2006-9b58-2d4e-8b5fea0076a1@linux.vnet.ibm.com>
On 9/14/23 06:45, Surya Kumari Jangala wrote:
> ira: Consider save/restore costs of callee-save registers [PR110071]
>
> In improve_allocation() routine, IRA checks for each allocno if spilling
> any conflicting allocnos can improve the allocation of this allocno.
> This routine computes the cost improvement for usage of each profitable
> hard register for a given allocno. The existing code in
> improve_allocation() does not consider the save/restore costs of callee
> save registers while computing the cost improvement.
>
> This can result in a callee save register being assigned to a pseudo
> that is live in the entire function and across a call, overriding a
> non-callee save register assigned to the pseudo by graph coloring. So
> the entry basic block requires a prolog, thereby causing shrink wrap to
> fail.
Yes, that can be a problem. The general idea is ok for me and common
sense says me that the performance should be better but I would like to
benchmark the patch on x86-64 spec2017 first. Real applications have
high register pressure and results might be not what we expect. So I'll
do it, report the results, and give my approval if there is no big
performance degradation. I think the results will be ready on Monday.
next prev parent reply other threads:[~2023-09-15 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 10:45 Surya Kumari Jangala
2023-09-15 14:48 ` Vladimir Makarov [this message]
2023-09-18 14:29 ` Vladimir Makarov
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=695dda93-85a8-450a-0e6a-58da24884c06@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).