From: "Ian Bolton" <bolton@IceraSemi.com>
To: "Ian Bolton" <bolton@IceraSemi.com>, "Jeff Law" <law@redhat.com>,
"Dave Hudson" <gcc@blueteddy.net>
Cc: "Vladimir Makarov" <vmakarov@redhat.com>, <gcc@gcc.gnu.org>
Subject: RE: Understanding IRA
Date: Wed, 11 Nov 2009 15:19:00 -0000 [thread overview]
Message-ID: <4D60B0700D1DB54A8C0C6E9BE69163700C3A98CC@EXCHANGEVS.IceraSemi.local> (raw)
In-Reply-To: <4D60B0700D1DB54A8C0C6E9BE69163700C31FD21@EXCHANGEVS.IceraSemi.local>
Yesterday, I wrote:
> BTW, today I have achieved some good results with existing IRA by doing
> the following:
>
> 1) Changed the REG_ALLOC_ORDER so that TOP_CREGS are given out before
> BOTTOM_REGS. My previous hacked version worked by increasing the
> priority of those that wanted BOTTOM_REGS, so they got first pick; this
> new version makes them wait their turn, but ensures those with higher
> priority take TOP_CREGS before BOTTOM_REGS.
>
> The analogy, I think, is of giving out meals on an airplane. Most
> people will eat meat or vegetarian meals, whereas vegetarians only
> want vegetarian meals. My hacked version was effectively allowing
> the vegetarians to push to the front of the queue and get their meals;
> this new version works by encouraging the meat eaters to eat the meaty
> meals first, leaving more suitable meals for the vegetarians further
> down the plane.
>
> 2) I have forced propagation of allocnos to parent regions with the
> following hack in find_allocno_class_costs():
>
> {
> /* Propagate costs to upper levels in the region
> tree. */
> parent_a_num = ALLOCNO_NUM (parent_a);
> for (k = 0; k < cost_classes_num; k++)
> COSTS_OF_ALLOCNO (total_costs, parent_a_num)->cost[k]
> += COSTS_OF_ALLOCNO (total_costs, a_num)->cost[k];
> COSTS_OF_ALLOCNO (total_costs, parent_a_num)->mem_cost
> += COSTS_OF_ALLOCNO (total_costs, a_num)->mem_cost;
> /* BEGIN IGB-IRA CHANGE 2 */
> /* Force total_costs to propagate upwards, by setting
> allocno_costs to be total_costs */
> for (k = 0; k < cost_classes_num; k++)
> COSTS_OF_ALLOCNO (allocno_costs, parent_a_num)->cost[k]
> = COSTS_OF_ALLOCNO (total_costs, parent_a_num)->cost[k];
> COSTS_OF_ALLOCNO (allocno_costs, parent_a_num)->mem_cost
> = COSTS_OF_ALLOCNO (total_costs, parent_a_num)->mem_cost;
> /* END IGB-IRA CHANGE 2 */
> }
>
> I don't know why propagation isn't happening normally, but
> this total_costs hack achieves the same thing for me at the
> moment. Is there any information I could provide to help
> someone tell me why propagation isn't happening?
Good news! I have been able to remove my "total_costs" hack
above by instead commenting out the following line from ira_build()
in ira-build.c:
remove_unnecessary_regions (false);
For my situation at least, this function is preventing the
propagation of useful allocno information from region 1 to
region 0. Without my change, the allocation for a pseudo in
region 0 is not aware of how that pseudo will be used inside
a loop in region 1; the real impact of this is that we need
to then do a register move *inside the loop* into a valid
register class for the instruction in region 1.
I do not believe this will impact anyone with a regular
register set, but for any architecture where some instructions
can only use a subset of the register bank, I believe that
all regions are always necessary, since cost information
for each allocno is relevant and important.
I still need to do some more testing in regards this "fix",
but I wanted to put my findings out there as soon as possible
for comment from the experts.
next prev parent reply other threads:[~2009-11-11 15:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 17:36 Ian Bolton
2009-11-05 18:05 ` Ian Bolton
2009-11-06 12:53 ` Dave Hudson
2009-11-09 14:13 ` Ian Bolton
2009-11-10 12:19 ` Dave Hudson
2009-11-10 17:21 ` Jeff Law
2009-11-10 17:38 ` Ian Bolton
2009-11-11 15:19 ` Ian Bolton [this message]
2009-11-11 16:12 ` Jeff Law
2009-11-11 17:04 ` Vladimir Makarov
2009-11-11 18:36 ` Ian Bolton
2009-11-11 20:09 ` Ian Bolton
2009-11-16 17:35 ` Ian Bolton
[not found] ` <4B01BB87.6020902@redhat.com>
2009-11-19 15:41 ` Ian Bolton
[not found] ` <4B1451C7.2010207@redhat.com>
2009-12-02 20:29 ` Ian Bolton
2009-12-03 19:16 ` Jeff Law
2009-12-07 13:30 ` Ian Bolton
-- strict thread matches above, loose matches on Subject: below --
2009-10-16 14:22 Ian Bolton
2009-10-16 15:23 ` Vladimir Makarov
2009-10-16 16:19 ` Jeff Law
2009-10-19 19:21 ` Ian Bolton
2009-10-19 21:09 ` Vladimir Makarov
2009-10-23 7:33 ` Jeff Law
2009-11-04 17:52 ` Ian Bolton
2009-11-04 19:49 ` Jeff Law
2009-10-16 15:45 ` Vladimir Makarov
2009-11-03 16:29 ` Ian Bolton
2009-11-03 23:02 ` Jeff Law
2009-11-04 17:13 ` Vladimir Makarov
2009-11-05 0:23 ` Jeff Law
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=4D60B0700D1DB54A8C0C6E9BE69163700C3A98CC@EXCHANGEVS.IceraSemi.local \
--to=bolton@icerasemi.com \
--cc=gcc@blueteddy.net \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=vmakarov@redhat.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).