Lines Matching defs:method

92 override the ``runOnModule`` method with the following signature:
94 The ``runOnModule`` method
101 The ``runOnModule`` method performs the interesting work of the pass.  It
139 The ``doInitialization(CallGraph &)`` method
146 The ``doInitialization`` method is allowed to do most of the things that
148 functions, get pointers to functions, etc.  The ``doInitialization`` method is
150 SCCs being processed.  The ``doInitialization`` method call is not scheduled to
155 The ``runOnSCC`` method
162 The ``runOnSCC`` method performs the interesting work of the pass, and should
166 The ``doFinalization(CallGraph &)`` method
173 The ``doFinalization`` method is an infrequently used method that is called
205 The ``doInitialization(Module &)`` method
212 The ``doInitialization`` method is allowed to do most of the things that
214 get pointers to functions, etc.  The ``doInitialization`` method is designed to
216 being processed.  The ``doInitialization`` method call is not scheduled to
219 A good example of how this method should be used is the `LowerAllocations
223 method to get a reference to the ``malloc`` and ``free`` functions that it
228 The ``runOnFunction`` method
235 The ``runOnFunction`` method must be implemented by your subclass to do the
241 The ``doFinalization(Module &)`` method
248 The ``doFinalization`` method is an infrequently used method that is called
276 The ``doInitialization(Loop *, LPPassManager &)`` method
283 The ``doInitialization`` method is designed to do simple initialization type of
285 ``doInitialization`` method call is not scheduled to overlap with any other
291 The ``runOnLoop`` method
298 The ``runOnLoop`` method must be implemented by your subclass to do the
303 The ``doFinalization()`` method
310 The ``doFinalization`` method is an infrequently used method that is called
329 The ``doInitialization(Region *, RGPassManager &)`` method
336 The ``doInitialization`` method is designed to do simple initialization type of
338 ``doInitialization`` method call is not scheduled to overlap with any other
344 The ``runOnRegion`` method
351 The ``runOnRegion`` method must be implemented by your subclass to do the
356 The ``doFinalization()`` method
363 The ``doFinalization`` method is an infrequently used method that is called
393 The ``runOnMachineFunction(MachineFunction &MF)`` method
401 ``MachineFunctionPass``; that is, you should override this method to do the
404 The ``runOnMachineFunction`` method is called on every ``MachineFunction`` in a
408 ``MachineFunction``'s ``getFunction()`` accessor method --- but remember, you
424 print method:
426 The ``print`` method
433 The ``print`` method must be implemented by "analyses" in order to print a
436 works.  Use the opt ``-analyze`` argument to invoke this method.
462 <writing-an-llvm-pass-getAnalysisUsage>` method, it defaults to not having any
467 The ``getAnalysisUsage`` method
474 By implementing the ``getAnalysisUsage`` method, the required and invalidated
494 analyses chain, the ``addRequiredTransitive`` method should be used instead of
495 the ``addRequired`` method.  This informs the ``PassManager`` that the
498 The ``AnalysisUsage::addPreserved<>`` method
511 ``setPreservesAll`` method can be called to indicate that the pass does not
513 ``setPreservesCFG`` method can be used by transformations that change
538 The ``Pass::getAnalysis<>`` method is automatically inherited by your class,
541 method.  It takes a single template argument that specifies which pass class
551 This method call returns a reference to the pass desired.  You may get a
554 <writing-an-llvm-pass-getAnalysisUsage>` implementation.  This method can be
555 called by your ``run*`` method implementation, or by any other local method
556 invoked by your ``run*`` method.
574 ``getAnalysisIfAvailable`` method, which returns a pointer to the analysis if
635 method.  Not implementing when it should be implemented will have the effect of
669 The ``releaseMemory`` method
680 ``releaseMemory`` virtual method is the way to do this.
684 the :ref:`getAnalysis <writing-an-llvm-pass-getAnalysis>` method) you should
686 this internal state.  This method is called after the ``run*`` method for the
848 Once the :program:`opt` stops in the ``PassManager::run`` method you are now