Re: [PATCH, SMS 1/4] Fix calculation of row_rest_count

2011-06-15 Thread Ayal Zaks
Revital Eres wrote on 14/06/2011 09:27:32 AM: > From: Revital Eres > To: Ayal Zaks/Haifa/IBM@IBMIL > Cc: gcc-patches@gcc.gnu.org, Patch Tracking > Date: 14/06/2011 09:27 AM > Subject: Re: [PATCH, SMS 1/4] Fix calculation of row_rest_count > > Hello, > > > Ple

Re: [PATCH, SMS 1/4] Fix calculation of row_rest_count

2011-06-13 Thread Revital Eres
Hello, > Please add the following: > o A clarification that rows_length is used only (as an optimization) to > back off quickly from trying to schedule a node in a full row; that is, to > avoid running through futile DFA state transitions. > o An assert that ps->rows_length[i] equals the number of

Re: [PATCH, SMS 1/4] Fix calculation of row_rest_count

2011-05-30 Thread Revital Eres
Hello, > Please add the following: > o A clarification that rows_length is used only (as an optimization) to > back off quickly from trying to schedule a node in a full row; that is, to > avoid running through futile DFA state transitions. > o An assert that ps->rows_length[i] equals the number of

Re: [PATCH, SMS 1/4] Fix calculation of row_rest_count

2011-05-29 Thread Ayal Zaks
> The calculation of the number of instructions in a row is currently > done by updating row_rest_count field in struct ps_insn on the fly > while creating a new instruction. It is used to make sure we do not > exceed > the issue_rate. > This calculation assumes the instruction is inserted in the

[PATCH, SMS 1/4] Fix calculation of row_rest_count

2011-05-18 Thread Revital Eres
Hello, The calculation of the number of instructions in a row is currently done by updating row_rest_count field in struct ps_insn on the fly while creating a new instruction. It is used to make sure we do not exceed the issue_rate. This calculation assumes the instruction is inserted in the begi