Lines Matching full:program
60 can be compiled and linked into a stand-alone program that can be
65 flags, and then executed to capture the program output and timing
67 output to ensure that the program is being compiled correctly.
69 In addition to compiling and executing programs, whole program tests
144 For more information on using the :program:`lit` tool, see ``llvm-lit --help``
163 The LLVM regression tests are driven by :program:`lit` and are located in the
180 have a ``lit.local.cfg`` file. :program:`lit` looks for this file to determine
189 Each test file must contain lines starting with "RUN:" that tell :program:`lit`
190 how to run it. If there are no RUN lines, :program:`lit` will issue an error
193 RUN lines are specified in the comments of the test program using the
195 to execute. Together, these lines form the "script" that :program:`lit`
199 script, they are not. RUN lines are interpreted by :program:`lit`.
203 :program:`lit` performs substitution on each RUN line to replace LLVM tool names
205 ``$(LLVM_OBJ_ROOT)/$(BuildMode)/bin)``. This ensures that :program:`lit` does
214 execution. :program:`lit` will substitute variables and arrange for the pipeline
230 your RUN lines. In general nothing needs to be quoted. :program:`lit` won't
231 strip off any quote characters so they will get passed to the invoked program.
232 To avoid this use curly braces to tell :program:`lit` that it should treat
245 tested outputs a full path to the input file. For example, :program:`opt` by
276 :program:`opt` does not output a ``ModuleID`` when input comes from stdin.
413 to check the error output). However, any program in a pipeline that
426 in the comments of the test program followed by a colon and one or more
439 To make the output more useful, :program:`lit` will scan
452 program, not the instructions to the test case, and
462 all of the programs, so that the output of the executed program can be
