[llvm-dev] mischeduler

[Andrew Trick via llvm-dev]

> On Nov 3, 2016, at 1:13 AM, Jonas Paulsson <paulsson at linux.vnet.ibm.com> wrote:
> 
> Hi Andy,
> 
> 
>> Intuitively, I think the code is sensible and the comment misleading. It should probably say something like:
>> 
>>  For loops that are acyclic path limited, aggressively schedule for latency. Within an single cycle, whenever CurrMOps > 0, allow normal heuristics to take precedence.
> 
> I changed the comment -- see attached patch.

LGTM!
-Andy

> 
> 
>> The concept here is to aggressively prioritize scheduling for latency in PostRA mode—unless the unscheduled instructions are clearly resource limited. I agree with your comment. Not sure what your question is ;)
> That's actually making sense to me now - sorry. I was confusing "policy" and "candidate evaluation".
> 
> /Jonas
> 
> <MISched_comment_acycliclat.patch>