Lines Matching full:program
41 the program being compiled. It does not modify the program at all, it just
79 :program:`opt` or :program:`bugpoint` tools via their :option:`-load` options.
220 :program:`opt` command to run an LLVM program through your pass. Because you
222 :program:`opt` tool to access it, once loaded.
226 the program through our transformation like this (or course, any bitcode file
236 The :option:`-load` option specifies that :program:`opt` should load your pass
240 the program in any interesting way, we just throw away the result of
241 :program:`opt` (sending it to ``/dev/null``).
244 :program:`opt` with the :option:`-help` option:
266 documentation to users of :program:`opt`. Now that you have a working pass,
293 passes listed are automatically inserted by the :program:`opt` tool to verify
341 ``ModulePass`` indicates that your pass uses the entire program as a unit,
375 passes that need to traverse the program bottom-up on the call graph (callees
391 reflect any changes made to the program.
400 described below should return ``true`` if they modified the program, or
439 <writing-an-llvm-pass-runOnFunction>` for every function in the program being
450 ``FunctionPass`` execute on each function in the program independent of all of
451 the other functions in the program. ``FunctionPass``\ es do not require that
466 of these methods should return ``true`` if they modified the program, or
516 <writing-an-llvm-pass-runOnFunction>` for every function in the program being
531 these methods should return ``true`` if they modified the program, or ``false``
570 <writing-an-llvm-pass-runOnLoop>` for every loop in the program being compiled.
585 return ``true`` if they modified the program, or ``false`` if they did not.
623 <writing-an-llvm-pass-runOnRegion>` for every region in the program being
687 <writing-an-llvm-pass-runOnBasicBlock>` for every ``BasicBlock`` in the program
694 the machine-dependent representation of each LLVM function in the program.
698 generally be run from the :program:`opt` or :program:`bugpoint` commands.
745 line to specify that the pass should be added to a program (for example, with
746 :program:`opt` or :program:`bugpoint`). The first argument is the name of the
767 program that has been analyzed. Note however that this pointer may be ``NULL``
839 modify the LLVM program at all (which is true for analyses), and the
841 instructions in the program but do not modify the CFG or terminator
855 // This example modifies the program, but does not modify the CFG
1061 #. **Pipeline the execution of passes on the program.** The ``PassManager``
1068 function, etc... until the entire program has been run through the passes.
1071 touching the LLVM program representation for a single function at a time,
1072 instead of traversing the entire program. It reduces the memory consumption
1124 the :program:`opt` tool), which uses the dominator set to check that the
1166 // We don't modify the program, so we preserve all analyses
1305 :program:`llc`/:program:`lli` tools, add your creator function's global
1346 transformation invoked by :program:`opt`, although nothing described here
1366 Note that :program:`opt` has a lot of debugging information in it, so it takes
1378 Starting program: opt test.bc -load $(LLVMTOP)/llvm/Debug+Asserts/lib/[libname].so -[passoption]
1383 Once the :program:`opt` stops in the ``PassManager::run`` method you are now
1399 * Restarting the program breaks breakpoints. After following the information
1401 Nex thing you know, you restart the program (i.e., you type "``run``" again),
1404 already set in your pass, run the program, and re-set the breakpoints once
1429 to be hacking on different parts of the program at the same time.
