search for: currcycl

On Dec 16, 2013, at 4:26 PM, Hal Finkel <hfinkel at anl.gov> wrote: >> At the end of each iteration, quality of generated code is estimated >> by >> executing newly introduced target dependent pass. Based on results >> path for >> the following iteration is calculated. At the moment, this has been >> proved >> for MIPS only and it is based on code

...(1). There is also the fact that IsResourceLimited =       checkResourceLimit(SchedModel->getLatencyFactor(), getCriticalCount(),                          getScheduledLatency()); , which is to me admittedly hard to grasp, but it seems that the scheduled latency (std::max(ExpectedLatency, CurrCycle)) affects the resource heuristic so that if scheduled latency is low enough, it becomes active. This then means that CurrCycle actually affects when resource balancing goes into action, and CurrCycle in turn is advanced when NumMicroOps reach the IssueWidth. So somehow it all depends on modellin...

...act that > > IsResourceLimited = > checkResourceLimit(SchedModel->getLatencyFactor(), getCriticalCount(), > getScheduledLatency()); > > , which is to me admittedly hard to grasp, but it seems that the scheduled latency (std::max(ExpectedLatency, CurrCycle)) > affects the resource heuristic so that if scheduled latency is low enough, it becomes active. This then means that CurrCycle > actually affects when resource balancing goes into action, and CurrCycle in turn is advanced when NumMicroOps reach the > IssueWidth. So somehow it all depend...