Ayal Zaks writes:
> On Wed, Sep 28, 2011 at 4:53 PM, Richard Sandiford
> wrote:
>> Ayal Zaks writes:
> Only request is to document that the register moves are
> placed/assigned-id's in a specific order.
I suppose this is the downside of splitting the patches up, sorry,
but t
On Wed, Sep 28, 2011 at 4:53 PM, Richard Sandiford
wrote:
> Ayal Zaks writes:
Only request is to document that the register moves are
placed/assigned-id's in a specific order.
>>>
>>>I suppose this is the downside of splitting the patches up, sorry,
>>>but the ids are only ordered for t
Ayal Zaks writes:
>>> Only request is to document that the register moves are
>>> placed/assigned-id's in a specific order.
>>
>>I suppose this is the downside of splitting the patches up, sorry,
>>but the ids are only ordered for the throw-away loop:
>>
>> FOR_EACH_VEC_ELT_REVERSE (ps_reg_move_in
e = SCHED_FIRST_REG_MOVE (u) + (i_reg_moves - 1);
Ayal.
2011/9/22 Richard Sandiford
>
> Ayal Zaks writes:
> > Richard Sandiford wrote on 30/08/2011
> > 03:10:50 PM:
> >
> >> From: Richard Sandiford
> >> To: gcc-patches@gcc.gnu.org
> >&
Ayal Zaks writes:
> Richard Sandiford wrote on 30/08/2011
> 03:10:50 PM:
>
>> From: Richard Sandiford
>> To: gcc-patches@gcc.gnu.org
>> Cc: Ayal Zaks/Haifa/IBM@IBMIL
>> Date: 30/08/2011 03:10 PM
>> Subject: [3/4] SMS: Record moves in the partial schedule
Richard Sandiford wrote on 30/08/2011
03:10:50 PM:
> From: Richard Sandiford
> To: gcc-patches@gcc.gnu.org
> Cc: Ayal Zaks/Haifa/IBM@IBMIL
> Date: 30/08/2011 03:10 PM
> Subject: [3/4] SMS: Record moves in the partial schedule
>
> This patch adds infrastructure that will
This patch adds infrastructure that will be used by the final patch.
Specifically:
- it splits the generation of register moves into two: schedule_reg_moves
records moves in the partial schedule, while apply_reg_moves makes the
register substitutions.
This patch doesn't actually sch