| /llvm-project/llvm/test/tools/llvm-dwarfutil/ |
| H A D | error-positional-args.test | 2 ## number of positional arguments is specified. 7 # CHECK1: error: exactly two positional arguments expected, 1 provided 8 # CHECK3: error: exactly two positional arguments expected, 3 provided
|
| /llvm-project/llvm/test/MC/AsmParser/ |
| H A D | macro-arg-err.s | 12 # CHECK-NEXT:{{.*}}.s:[[#@LINE+6]]:14: error: too many positional arguments 33 # CHECK-NEXT:{{.*}}.s:[[#@LINE+3]]:14: error: too many positional arguments 38 # CHECK-NEXT:{{.*}}.s:[[#@LINE+3]]:20: error: cannot mix positional and keyword arguments
|
| /llvm-project/mlir/include/mlir/Dialect/PDL/IR/ |
| H A D | PDLTypes.td | 106 // A range of positional values of one of the provided types. 114 // Either a positional value or a range of positional values for a given type.
|
| /llvm-project/llvm/test/tools/llvm-profdata/ |
| H A D | errors.test | 2 SHOW-REQ: the positional argument '<profdata-file>' is required unless '--debug-info' is provided
|
| /llvm-project/lldb/test/Shell/ScriptInterpreter/Python/Crashlog/ |
| H A D | no-args.test | 7 # CHECK: positional arguments:
|
| /llvm-project/llvm/test/tools/llvm-reduce/ |
| H A D | command-line-behavior.test | 9 # RUN: not llvm-reduce --test FileCheck 2>&1 | grep "error: reduction testcase positional argument …
|
| /llvm-project/llvm/docs/ |
| H A D | CommandLine.rst | 65 options often found in real programs. For example, `positional`_ arguments, 150 with helper functions like `cl::desc(...)`_, so there are no positional 157 argument, the CommandLine library allows for `positional`_ arguments to be 158 specified for the program. These positional arguments are filled with command 166 This declaration indicates that the first positional argument should be treated 516 positional arguments together if there may be more than one specified. In the 712 file, but will not have an ordering defined if the positional arguments are 714 all of your positional arguments in one .cpp file. 716 Specifying positional options with hyphens 719 Sometimes you may want to specify a value to your positional argument that [all …]
|
| /llvm-project/mlir/test/Dialect/Linalg/ |
| H A D | match-ops.mlir | 7 // Checking the syntax of positional specifications.
|
| /llvm-project/mlir/include/mlir/Dialect/PDLInterp/IR/ |
| H A D | PDLInterpOps.td | 64 // Check operations evaluate a predicate on a positional value and then 74 // Switch operations evaluate a predicate on a positional value and then 87 let summary = "Apply a constraint to a set of positional values"; 90 has been registered with the interpreter, with a given set of positional 125 successful match. The rewrite is passed a set of positional arguments. The 155 let summary = "Check if two positional values or ranges are equivalent"; 157 `pdl_interp.are_equal` operations compare two positional values for 988 let summary = "Check if a positional value is non-null"; 990 `pdl_interp.is_not_null` operations check that a positional value or range
|
| /llvm-project/llvm/test/FileCheck/dump-input/ |
| H A D | enable.txt | 26 ; No positional arg. 41 ; No positional arg.
|
| /llvm-project/mlir/utils/mbr/ |
| H A D | README.md | 75 If you want to run only specific benchmarks, you can use the positional argument
|
| /llvm-project/llvm/docs/CommandGuide/ |
| H A D | llvm-symbolizer.rst | 25 input or as positional arguments on the command-line. By default, input names 31 A positional argument or standard input value can be preceded by "DATA" or
|
| H A D | llvm-profdata.rst | 51 Profiles passed in via ``-weighted-input``, ``-input-files``, or via positional
|
| /llvm-project/lldb/docs/man/ |
| H A D | lldb-server.rst | 159 and the arguments to the debugged executable as positional arguments.
|
| H A D | lldb.rst | 258 Passing an executable as a positional argument prepares lldb to debug the given
|
| /llvm-project/clang-tools-extra/docs/clang-tidy/checks/modernize/ |
| H A D | use-std-print.rst | 49 - It supports field widths, precision, positional arguments, leading zeros,
|
| /llvm-project/clang/docs/ |
| H A D | LibTooling.rst | 183 the build path as first argument and some source files as further positional
|
| H A D | ObjectiveCLiterals.rst | 209 // Partition command line arguments into positional and option arguments. 217 [args addObject:@(arg)]; // positional argument
|
| H A D | ClangFormat.rst | 298 positional arguments:
|
| /llvm-project/llvm/test/CodeGen/X86/ |
| H A D | callbr-asm-outputs.ll | 218 ; Test5 - test that we don't rely on a positional constraint. ie. +r in
|
| /llvm-project/mlir/include/mlir/IR/ |
| H A D | PatternBase.td | 139 // then positional placeholders are also supported; placeholder `$N` in the
|
| /llvm-project/llvm/docs/DirectX/ |
| H A D | DXILOpTableGenDesign.rst | |
| /llvm-project/lldb/docs/resources/ |
| H A D | build.rst | 206 build-tree\ :sup:`1` and the positional argument pointing to the ``llvm`` 218 main build-tree and the positional argument pointing to the ``lldb`` directory
|
| /llvm-project/mlir/docs/ |
| H A D | DeclarativeRewrites.md | 387 *positional placeholder* and *positional range placeholder*.
|
| /llvm-project/third-party/unittest/googletest/src/ |
| H A D | gtest.cc | 6696 absl::flat_hash_set<char*> positional; in ParseGoogleTestFlagsOnly() local 6698 positional.insert(arg); in ParseGoogleTestFlagsOnly() 6722 if (positional.contains(arg)) { in ParseGoogleTestFlagsOnly()
|