Lines Matching refs:parameters

92   let parameters = (ins "unsigned":$width);
102   /// Indicate that our type will add additional verification to the parameters.
129   /// Here we've defined two parameters, one is the `self` type of the attribute
132   let parameters = (ins AttributeSelfTypeParameter<"">:$type, "APInt":$value);
151   /// Indicate that our attribute will add additional verification to the parameters.
180 The `mnemonic` field, i.e. the template parameters `attrMnemonic` and
190 The `parameters` field is a variable length list containing the attribute or
191 type's parameters. If no parameters are specified (the default), this type is
210 additional functionality. This is generally useful for complex parameters, or those
215 may suggest, `AttrParameter` is intended for parameters on Attributes,
216 `TypeParameter` for Type parameters, and `AttrOrTypeParameters` for either.
222 let parameters = (ins "ArrayRef<int>":$dims);
226 constructor blindly copies parameters by value. It does not know anything about
244 let parameters = (ins ArrayRefIntParam:$dims);
297 automatically generated based on the parameters of the type. These are used to
303   let parameters = (ins "int":$intParam);
310 // Builders are named `get`, and return a new instance for a given set of parameters.
336   let parameters = (ins "int":$intParam);
491 and Types with no parameters need not use either of these fields, in which case
557   // Define two parameters whose C++ types are indicated in string literals.
558   let parameters = (ins "int":$count, "AffineMap":$map);
576 parameters are parsed or printed.
636 these parameters are expected to return `FailureOr<$cppStorageType>`.
639 parameter, parameters can override `convertFromStorage`, which by default is
644 Optional parameters in the assembly format can be indicated by setting
660 Only optional parameters or directives that only capture optional parameters can
671 are used inside optional groups are allowed only if all captured parameters are
676 Optional parameters can be given default values by setting `defaultValue`, a
686 let parameters = (ins DefaultValuedParameter<"Optional<int>", "5">:$a)
698 For optional `Attribute` or `Type` parameters, the current MLIR context is
709 - `params`: capture all parameters of an attribute or type.
719 This directive is used to refer to all parameters of an attribute or type. When
721 comma-separated list of the parameters. For example:
725   let parameters = (ins "int":$a, "int":$b);
738 as an argument that refers to all parameters in place of explicitly listing all
739 parameters as variables.
743 This directive can be used to wrap attribute or type parameters such that they
751   let parameters = (ins MyPairType:$inner);
756   let parameters = (ins MyPairType:$inner);
769 If optional parameters are present, they are not printed in the parameter list
782   let parameters = (ins StringRefParameter<>:$sym_name,
790 parameters captured in the directive.
798 all the parameters of the attribute or type. For the same type above, an
805 The order in which the parameters are printed is the order in which they are
814 let parameters = (ins "int":$foo, "int":$bar);
847 bound parameters have failure values afterwards.
854 - `static LogicalResult verify(function_ref<InFlightDiagnostic()> emitError, parameters...)`
856 These methods are used to verify the parameters provided to the attribute or
860 - `AttrOrType getChecked(function_ref<InFlightDiagnostic()> emitError, parameters...)`
889   of the storage parameters.
930   /// the given parameters.
950 being said, some parameters may be treated as "mutable" and modified after
951 construction. Mutable parameters should be reserved for parameters that can not
953 these parameters do not take part in the uniquing of the Attribute or Type.
955 TODO: Mutable parameters are currently not supported in the declarative