Lines Matching full:example
66 somewhere underneath this directory. For example, it can be a small
78 for an example of such test.
156 variable to pass the required options to lit. For example, you can use:
165 script which is built as part of LLVM. For example, to run the
255 Below is an example of legal RUN lines in a ``.ll`` file:
289 For example to generate assertions in an :program:`llc`-based test, after
353 (for example, "See PR999 for more details").
355 example, do not use patterns like ``br i1 undef``, which are likely to break
359 - Outside PhaseOrdering tests, only run a minimal set of passes. For example,
373 using ``split-file`` to extract them. For example,
395 For example, consider ``test/Linker/ident.ll``. The directory structure is
525 tested outputs a full path to the input file. For example, :program:`opt` by
530 $ cat example.ll
535 $ opt -S /path/to/example.ll
536 ; ModuleID = '/path/to/example.ll'
542 ``ModuleID`` can unexpectedly match against ``CHECK`` lines. For example:
567 The first problem is to check for target-specific output, for example sizes
568 of structures, paths and architecture names, for example:
589 of a specific sub-architecture, for example only to Intel chips that support ``AVX2``.
624 Some tests are expected to fail. For example, there may be a known bug
645 expressions can appear inside an identifier, so for example ``he{{l+}}o`` would match
647 - The default target triple, preceded by the string ``target=`` (for example,
649 to match parts of the triple (for example, ``target={{.*}}-windows{{.*}}``
693 example, ``target=mips{{.*}}`` will match not only mips, but also mipsel,
702 example, to match both freebsd and netbsd in an expression, you could write
721 Example: ``/home/user/llvm/test/MC/ELF/foo_test.s``
726 Example: ``/home/user/llvm/test/MC/ELF``
734 Example: ``/home/user/llvm.build/test/MC/ELF/Output/foo_test.s.tmp``
742 Example: ``/home/user/llvm.build/test/MC/ELF/Output``
765 Example: ``%s: C:\Desktop Files/foo_test.s.tmp``
767 Example: ``%/s: C:/Desktop Files/foo_test.s.tmp``
775 Example: ``%s: S:\foo_test.s.tmp``
777 Example: ``%{/s:real}: C:/SDrive/foo_test.s.tmp``
785 Example: ``%s: C:\Desktop Files\foo_test.s.tmp``
787 Example: ``%:s: C\Desktop Files\foo_test.s.tmp``
797 Example: ``Linux %errc_ENOENT: No such file or directory``
799 Example: ``Windows %errc_ENOENT: no such file or directory``
814 For example, this can be used in tests with multiple RUN lines,
823 Example: ``.so`` (Linux), ``.dylib`` (macOS), ``.dll`` (Windows)
829 Example: ``.exe`` (Windows), empty on Linux.
850 the desired ABI. For example, if the test suite is running with the
879 For example, the following directives can be inserted into a test file to define
917 parameter substitutions in the above example serve a second purpose: they
939 example above.
1010 ``RUN:`` line unexpanded. For example, the following directives refer to
1040 the above example, setting the limit to 2 would cause lit to make a second pass
1049 line has stopped changing. In the above example, setting the limit higher than
1053 and report an error if the ``RUN:`` line changes again. In the above example,
1065 Example:
1081 their name. For example: