Home | History | Annotate | Download | only in CodeGen

Lines Matching full:scheduled

485       // scheduler for the top of it's scheduled region.
559 // SU->TopReadyCycle was set to CurrCycle when it was scheduled. However,
598 // SU->BotReadyCycle was set to CurrCycle when it was scheduled. However,
619 /// that don't get scheduled.
696 assert(!SU->isScheduled && "Node already scheduled");
722 // This sets the scheduled node's ReadyCycle to CurrCycle. When updateQueues
857 /// that don't get scheduled.
874 // Setup the register pressure trackers for the top scheduled top and bottom
875 // scheduled regions.
923 // the max pressure in the scheduled code for these sets.
1071 assert(!SU->isScheduled && "Node already scheduled");
1241 // Update top scheduled pressure.
1267 // Update bottom scheduled pressure.
1742 /// scheduled.
1849 assert(SU->getInstr() && "Scheduled SUnit must have instr");
1853 // scheduled, but CurrCycle may have been eagerly advanced immediately after
1870 // Record this node as an immediate dependent of the scheduled node.
1888 /// Move the boundary of scheduled code by one cycle.
1933 /// Add the given processor resource to this scheduled zone.
1970 /// Move the boundary of scheduled code by one SUnit.
1975 // Calls are scheduled with their preceding instructions. For bottom-up
2005 // scheduled MOps to be "retired". We do loosely model in-order resource
2020 // Scale scheduled micro-ops for comparing with the critical resource.
2234 // max height/depth of scheduled nodes minus the cycles since it was
2235 // scheduled:
2629 // If we have already scheduled the physreg produce/consumer, immediately
2651 /// \param Zone describes the scheduled zone that we are extending.
2652 /// \param RPTracker describes reg pressure within the scheduled zone.
2711 // Avoid increasing the max critical pressure in the scheduled region.
2719 // This can result in very long dependence chains scheduled in sequence, so
2772 // Prefer immediate defs/users of the last scheduled instruction. This is a
2790 /// maintain the number of vreg uses remaining to be top-scheduled.
2847 // RegionCriticalPSets summarizes the pressure within the scheduled region and
2929 // Find already scheduled copies with a single physreg dependence and move
2930 // them just above the scheduled instruction.
3112 /// Called after ScheduleDAGMI has scheduled an instruction and updated
3113 /// scheduled/remaining flags in the DAG nodes.
3205 /// \brief Scheduler callback to notify that a new subtree is scheduled.
3210 /// Callback after a node is scheduled. Mark a newly scheduled tree, notify
3261 // instructions to be scheduled first.