Lines Matching defs:code

32 1.  middle case: duplication of verification across the code base, or
47     operation into the record, so that readers don't need to jump among code
511 The second and third forms are good for use in manually written code, given that
574 generated as is in the C++ code, they should be valid C++ constructs for a type
579 code block as follows.
597 no limitation on the code size, we encourage one to define only short builders
615 The generated code will use default value in the declaration, but not in the
637 ### Custom verifier code
639 Verification code will be automatically generated for
852 when generating the C++ code for the format. The `UserDirective` is an
857 strings of C++ code. The type directives must refer to a variable, but that
931 A custom directive can take a string of C++ code as a parameter. The code is
1132 code that is added to the generated source file inside the op's C++ namespace.
1135 ### Generated C++ code
1138 generates two files containing the corresponding C++ code: one for declarations,
1363 and C++. What is inside is already C++ code, which will be treated as opaque
1366 You can put any C++ code that returns a boolean value inside a `CPred`,
1393 just call `attr.isa<IntegerAttr>()`. The code can be wrapped in a `CPred` as
1731 `--gen-op-defs` as explained in [Generated C++ code](#generated-c-code).
1733 To see the generated code, invoke `mlir-tblgen` with a specific generator by
1788 every code generator separately.
1801 *   Ops registered using a registry separate from C++ code.