Searched refs:argN (Results 1 – 6 of 6) sorted by relevance
| /external/tensorflow/tensorflow/compiler/aot/ |
| D | codegen_test_h.golden | 37 // // ...set args using computation.argN methods
119 // T& argN(...dim indices...)
|
| /external/llvm-project/mlir/lib/Dialect/Linalg/Transforms/ |
| D | Sparsification.cpp | 364 unsigned argN = arg.getArgNumber(); in buildTensorExp() local
368 auto map = op.getIndexingMap(argN); in buildTensorExp()
370 return merger.addExp(Kind::kTensor, argN); in buildTensorExp()
|
| /external/llvm-project/mlir/docs/ |
| D | DeclarativeRewrites.md | 93 [directives](#special-directives). `argN` is for matching (if used in source
100 `argN` can be a `dag` object itself, thus we can have nested `dag` tree to model
|
| D | OpDefinitions.md | 70 arg0, arg1, argN)`. The operator can be any TableGen `def`; an argument can
|
| /external/llvm-project/mlir/include/mlir/IR/ |
| D | OpBase.td | 2296 // In the source pattern, `argN` can be used to specify matchers (e.g., using
2304 // In the result pattern, `argN` can be used to refer to a previously bound
2305 // name, with potential transformations (e.g., using tAttr, etc.). `argN` can
2390 // If used as a DAG node, i.e., `(NativeCodeCall<"..."> <arg0>, ..., <argN>)`,
2392 // wrapped C++ expression will be replaced by `<argN>`.
|
| /external/bcc/tools/ |
| D | trace_example.txt | 93 The reason is that the default type for argN and retval is an unsigned 64-bit
|