Lines Matching full:writing

2 Writing an LLVM Pass
23 <writing-an-llvm-pass-ModulePass>` , :ref:`CallGraphSCCPass
24 <writing-an-llvm-pass-CallGraphSCCPass>`, :ref:`FunctionPass
25 <writing-an-llvm-pass-FunctionPass>` , or :ref:`LoopPass
26 <writing-an-llvm-pass-LoopPass>`, or :ref:`RegionPass
27 <writing-an-llvm-pass-RegionPass>` classes, which gives the system more
41 Quick Start --- Writing hello world
104 Which are needed because we are writing a `Pass
137 <writing-an-llvm-pass-FunctionPass>`.  The different builtin pass subclasses
138 are described in detail :ref:`later <writing-an-llvm-pass-pass-classes>`, but
159 We declare a :ref:`runOnFunction <writing-an-llvm-pass-runOnFunction>` method,
161 <writing-an-llvm-pass-FunctionPass>`.  This is where we are supposed to do our
177 Lastly, we :ref:`register our class <writing-an-llvm-pass-registration>`
262 <writing-an-llvm-pass-registration>`).  Because the Hello pass does not modify
291 pass is.  The :ref:`PassManager <writing-an-llvm-pass-passmanager>` provides a
328 <writing-an-llvm-pass-basiccode>` example uses the :ref:`FunctionPass
329 <writing-an-llvm-pass-FunctionPass>` class for its implementation, but we did
401 :ref:`FunctionPass <writing-an-llvm-pass-FunctionPass>`, you should derive from
416    <writing-an-llvm-pass-runOnSCC>` (including global data).
459 <writing-an-llvm-pass-runOnSCC>` for every SCC in the program being compiled.
480    <writing-an-llvm-pass-runOnFunction>` (including global data).
483 World <writing-an-llvm-pass-basiccode>` pass for example).
535 <writing-an-llvm-pass-runOnFunction>` for every function in the program being
597 <writing-an-llvm-pass-runOnLoop>` for every loop in the program being compiled.
604 ``RegionPass`` is similar to :ref:`LoopPass <writing-an-llvm-pass-LoopPass>`,
650 <writing-an-llvm-pass-runOnRegion>` for every region in the program being
674    <writing-an-llvm-pass-runOnMachineFunction>` (including global data).
702 In the :ref:`Hello World <writing-an-llvm-pass-basiccode>` example pass we
743 :ref:`optimize the execution of passes <writing-an-llvm-pass-passmanager>` it
753 <writing-an-llvm-pass-getAnalysisUsage>` method, it defaults to not having any
831 with the :ref:`getAnalysisUsage <writing-an-llvm-pass-getAnalysisUsage>`
845 <writing-an-llvm-pass-getAnalysisUsage>` implementation.  This method can be
906 <writing-an-llvm-pass-passmanager>` scans the available passes to see if any
909 :ref:`interaction between passes <writing-an-llvm-pass-interaction>` still
912 Although :ref:`Pass Registration <writing-an-llvm-pass-registration>` is
915 <writing-an-llvm-pass-RegisterAnalysisGroup>` template to join the
918 <writing-an-llvm-pass-RegisterAnalysisGroup>`.
1008 passes, ensures their :ref:`prerequisites <writing-an-llvm-pass-interaction>`
1021    <writing-an-llvm-pass-releaseMemory>` allocated to holding analysis results
1027    of consecutive :ref:`FunctionPass <writing-an-llvm-pass-FunctionPass>`, it
1029    <writing-an-llvm-pass-FunctionPass>` on the first function, then all of the
1030    :ref:`FunctionPasses <writing-an-llvm-pass-FunctionPass>` on the second
1039    :ref:`interesting enhancements <writing-an-llvm-pass-SMP>` in the future.
1044 unimplemented :ref:`getAnalysisUsage <writing-an-llvm-pass-getAnalysisUsage>`
1055 :ref:`Hello World <writing-an-llvm-pass-basiccode>` pass interacts with other
1089 <writing-an-llvm-pass-basiccode>` pass in between the two passes:
1117 Here we see that the :ref:`Hello World <writing-an-llvm-pass-basiccode>` pass
1120 <writing-an-llvm-pass-getAnalysisUsage>` method to our pass:
1175 If you are writing an analysis or any other pass that retains a significant
1177 the :ref:`getAnalysis <writing-an-llvm-pass-getAnalysis>` method) you should