Lines Matching refs:Latency
57 "which tries to balance latency and register pressure",
113 /// NeedLatency - True if the scheduler will make use of latency information.
121 /// been issued, but their results are not ready yet (due to the latency of
263 /// need actual latency information but the hybrid scheduler does.
606 // Bypass lots of virtual calls in case of long latency.
628 // But given the crude nature of modeling latency though such nodes, we
634 // Bump CurCycle to account for latency. We assume the latency of other
777 // Check AvailableQueue after ReleasePredecessors in case of zero latency.
1082 D.setLatency(LoadSU->Latency);
1172 FromDep.setLatency(SU->Latency);
1175 ToDep.setLatency(CopyFromSU->Latency);
1354 /// (1) Ready: latency has been satisfied
2330 // Check for either a dependence (latency) or resource (hazard) stall.
2342 // Return 0 if latency-based priority is equivalent.
2346 // been scheduled will induce a copy. Model this as an extra cycle of latency.
2368 // If either node is scheduling for latency, sort them by height/depth
2369 // and latency.
2383 DEBUG(dbgs() << " Comparing latency of SU (" << left->NodeNum
2388 if (left->Latency != right->Latency)
2389 return left->Latency > right->Latency ? 1 : -1;
2472 // Comparing latency against a call makes little sense unless the node
2545 // No way to compute latency of calls.
2611 // No way to compute latency of calls.
