Lines Matching full:manager

9 // This file implements the legacy LLVM Pass Manager infrastructure.
35 // See PassManagers.h for Pass Manager infrastructure overview.
92 // If it's a pass manager, don't emit a remark. (This hinges on the assumption
293 /// Pass Manager itself does not invalidate any analysis info.
356 // Execute all the passes managed by this top level manager.
409 /// Pass Manager itself does not invalidate any analysis info.
415 /// RequiredPass is run on the fly by Pass Manager when P requests it
425 StringRef getPassName() const override { return "Module Pass Manager"; }
430 // Print passes managed by this manager
432 dbgs().indent(Offset*2) << "ModulePass Manager\n";
497 /// Pass Manager itself does not invalidate any analysis info.
556 /// Initialize top level manager. Create first pass manager.
601 // If this pass has a corresponding pass manager, push higher level
602 // analysis to this pass manager.
662 /// the manager. Remove dead passes. This is a recursive function.
665 // TODO : Allocate function manager for this pass, other wise required set
666 // may be inserted into previous function manager
718 // Schedule analysis pass that is managed by the same pass manager.
722 // Schedule analysis pass that is managed by a new manager.
738 // top level manager. Set up analysis resolver to connect them.
756 // Add the requested pass to the best available pass manager.
819 // Print passes managed by this top level manager.
833 for (PMDataManager *Manager : PassManagers)
834 Manager->getAsPass()->dumpPassStructure(1);
892 // passes managed by this manager
949 // provided by parent manager then remove it here.
978 // If this is a on the fly manager then it does not have TPM.
1025 // This manager is going to manage pass P. Set up analysis resolver
1031 // then the F's manager, not F, records itself as a last user of M.
1060 // Keep track of higher level analysis used by this manager.
1067 // However, if P is a Pass Manager then it does not need
1159 // If this is a on the fly manager then it does not have TPM.
1272 /// RequiredPass is run on the fly by Pass Manager when P requests it
1274 /// This should be handled by specific pass manager.
1282 // (e.g. dominator info). Pass manager uses on the fly function pass manager
1283 // to provide this on demand. In that case, in Pass manager terminology,
1285 // lower level pass manager.
1287 // When Pass manager is not able to order required analysis info, Pass manager
1288 // checks whether any lower level manager will be able to provide this
1326 /// Create new Function pass manager
1329 // FPM is the top level manager.
1370 /// cleanup - After running all passes, clean up pass manager cache.
1385 /// Print passes managed by this manager
1387 dbgs().indent(Offset*2) << "FunctionPass Manager\n";
1404 // Collect inherited analysis from Module level pass manager.
1606 /// RequiredPass is run on the fly by Pass Manager when P requests it
1619 // FPP is the top level manager.
1664 /// Create new pass manager
1667 // PM is the top level manager
1691 // Pop Pass Manager from the stack and clear its analysis info.
1700 // Push PM on the stack and set its top level manager.
1702 assert(PM && "Unable to push. Pass Manager expected");
1703 assert(PM->getDepth()==0 && "Pass Manager depth set too early");
1707 && "pushing bad pass manager to PMStack");
1710 assert(TPM && "Unable to find top level manager");
1717 && "pushing bad pass manager to PMStack");
1724 // Dump content of the pass manager stack.
1726 for (PMDataManager *Manager : S)
1727 dbgs() << Manager->getAsPass()->getPassName() << ' ';
1733 /// Find appropriate Module Pass Manager in the PM Stack and
1734 /// add self into that manager.
1737 // Find Module Pass Manager
1745 /// Find appropriate Function Pass Manager or Call Graph Pass Manager
1746 /// in the PM Stack and add self into that manager.
1749 // Find Function Pass Manager
1754 // Create new Function Pass Manager if needed.
1756 // [1] Create new Function Pass Manager
1760 // [2] Set up new manager's top level manager
1763 // [3] Assign manager to manage this new manager. This may create
1767 // [4] Push new manager into PMS
1772 // Assign FPP as the manager of this pass.