From: Jeff Law <law@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"Vladimir N. Makarov" <vmakarov@redhat.com>
Subject: Re: Patch 10/9: track subwords of DImode allocnos
Date: Wed, 14 Jul 2010 19:06:00 -0000 [thread overview]
Message-ID: <4C3E0ABC.6090307@redhat.com> (raw)
In-Reply-To: <4C3CD626.3050600@codesourcery.com>
On 07/13/10 15:09, Bernd Schmidt wrote:
> On 07/13/2010 10:43 PM, Jeff Law wrote:
>
>
>> Overall this was relatively straightforward. You touched on most of the
>> non-obvious stuff above. Answers to most of my questions became clear
>> as wrote out the questions. Here's all that's left:
>>
>>
>> In assign_hard_reg, you moved this hunk:
>>
>> + if (allocno_coalesced_p)
>> + {
>> + if (bitmap_bit_p (processed_coalesced_allocno_bitmap,
>> + ALLOCNO_NUM (conflict_allocno)))
>> + continue;
>> + bitmap_set_bit (processed_coalesced_allocno_bitmap,
>> + ALLOCNO_NUM (conflict_allocno));
>> + }
>>
>> Into the ! ALLOCNO_MAY_BE_SPILLED_P if-clause rather than leaving it to
>> execute unconditionally for each conflict allocno. I don't see the
>> reasoning behind this change.
>>
> We've found a conflicting object, and looked up the corresponding
> allocno. There are two cases here, either the conflicting allocno has a
> hard register already, or it doesn't. In the first case, we need to
> track the conflicts by object, which means we can't ignore the conflict
> if we've seen the allocno previously - we might have seen a different
> subword. In the second case, we're just doing some costs bookkeeping,
> and here it's OK to skip the allocno if we've seen it before.
>
> Does that make sense?
>
Yes. Makes perfect sense now. I might have just been burned out when I
stumbled across that somewhat odd hunk.
jeff
prev parent reply other threads:[~2010-07-14 19:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 14:08 Patch 0/9: IRA cleanups and preparations for tracking subwords of DImode Bernd Schmidt
2010-06-18 14:08 ` Patch 1/9: Remove dead code Bernd Schmidt
2010-06-18 14:11 ` Jeff Law
2010-06-18 14:09 ` Patch 2/9: Split up and reorganize some functions Bernd Schmidt
2010-06-18 18:26 ` Jeff Law
2010-06-18 19:07 ` Bernd Schmidt
2010-06-21 16:08 ` Jeff Law
2010-06-21 16:21 ` Bernd Schmidt
2010-06-18 14:10 ` Patch 3/9: create some more small helper functions Bernd Schmidt
2010-06-18 22:07 ` Jeff Law
2010-06-18 14:11 ` Patch 4/9: minor formatting fix Bernd Schmidt
2010-06-18 14:19 ` Jeff Law
2010-06-18 14:12 ` Patch 5/9: rename allocno_set to minmax_set Bernd Schmidt
2010-06-18 14:42 ` Jeff Law
2010-06-18 14:25 ` Patch 6/9: remove "allocno" from live_range_t Bernd Schmidt
2010-06-18 18:16 ` Jeff Law
2010-06-25 2:22 ` Bernd Schmidt
2010-06-25 3:16 ` Jeff Law
2010-06-18 14:37 ` Patch 7/9: Introduce ira_object_t Bernd Schmidt
2010-06-18 22:07 ` Jeff Law
2010-06-18 14:48 ` Patch 8/9: track live ranges for objects Bernd Schmidt
2010-06-18 22:41 ` Jeff Law
2010-06-18 15:26 ` Patch 9/9: change FOR_EACH_ALLOCNO_CONFLICT to use objects Bernd Schmidt
2010-06-22 1:45 ` Jeff Law
2010-06-18 20:02 ` Patch 0/9: IRA cleanups and preparations for tracking subwords of DImode Vladimir N. Makarov
2010-06-18 20:11 ` Jeff Law
2010-06-21 18:01 ` Patch 10/9: track subwords of DImode allocnos Bernd Schmidt
2010-07-06 23:49 ` Ping: " Bernd Schmidt
2010-07-13 20:43 ` Jeff Law
2010-07-13 21:10 ` Bernd Schmidt
2010-07-13 22:01 ` Vladimir Makarov
2010-07-14 2:00 ` Bernd Schmidt
2010-07-22 18:00 ` Nathan Froyd
2010-07-22 18:25 ` Bernd Schmidt
2010-07-22 18:50 ` Nathan Froyd
2010-07-22 22:35 ` Bernd Schmidt
2010-07-25 1:23 ` H.J. Lu
2011-01-27 8:39 ` H.J. Lu
2010-07-20 14:28 ` Bernd Schmidt
2010-07-20 14:44 ` Vladimir Makarov
2010-07-22 15:49 ` Bernd Schmidt
2010-07-14 19:06 ` Jeff Law [this message]
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=4C3E0ABC.6090307@redhat.com \
--to=law@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--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).