Lines Matching refs:Parameters
71 MCAsmMacroParameters Parameters;
75 : Name(N), Body(B), Parameters(std::move(P)) {}
258 ArrayRef<MCAsmMacroParameter> Parameters);
260 ArrayRef<MCAsmMacroParameter> Parameters,
1906 ArrayRef<MCAsmMacroParameter> Parameters,
1909 unsigned NParameters = Parameters.size();
1910 bool HasVararg = NParameters ? Parameters.back().Vararg : false;
1914 // A macro without parameters is handled differently on Darwin:
1922 // This macro has no parameters, look for $0, $1, etc.
1931 // This macro has parameters, look for \foo, \bar, etc.
1989 if (Parameters[Index].Name == Argument)
2098 // Spaces can delimit parameters, but could also be part an expression.
2142 const unsigned NParameters = M ? M->Parameters.size() : 0;
2150 // - macros defined without any parameters accept an arbitrary number of them
2151 // - macros defined with parameters accept at most that many of them
2152 bool HasVararg = NParameters ? M->Parameters.back().Vararg : false;
2189 if (M->Parameters[FAI].Name == FA.Name)
2220 if (M->Parameters[FAI].Required) {
2223 "'" + M->Parameters[FAI].Name + "' in macro '" + M->Name + "'");
2227 if (!M->Parameters[FAI].Value.empty())
2228 A[FAI] = M->Parameters[FAI].Value;
2268 if (expandMacro(OS, Body, M->Parameters, A, true, getTok().getLoc()))
3402 /// ::= .macro name[,] [parameters]
3411 MCAsmMacroParameters Parameters;
3414 if (!Parameters.empty() && Parameters.back().Vararg)
3416 "Vararg parameter '" + Parameters.back().Name +
3417 "' should be last one in the list of parameters.");
3457 Parameters.push_back(std::move(Parameter));
3508 checkForBadMacro(DirectiveLoc, Name, Body, Parameters);
3509 defineMacro(Name, MCAsmMacro(Name, Body, std::move(Parameters)));
3515 /// With the support added for named parameters there may be code out there that
3516 /// is transitioning from positional parameters. In versions of gas that did
3517 /// not support named parameters they would be ignored on the macro definition.
3518 /// But to support both styles of parameters this is not possible so if a macro
3519 /// definition has named parameters but does not use them and has what appears
3520 /// to be positional parameters, strings like $1, $2, ... and $n, then issue a
3522 /// Hoping the developer will either remove the named parameters from the macro
3523 /// definition so the positional parameters get used if that was what was
3524 /// intended or change the macro to use the named parameters. It is possible
3525 /// this warning will trigger when the none of the named parameters are used
3529 ArrayRef<MCAsmMacroParameter> Parameters) {
3530 // If this macro is not defined with named parameters the warning we are
3532 unsigned NParameters = Parameters.size();
3539 // Look at the body of the macro for use of both the named parameters and what
3540 // are likely to be positional parameters. This is what expandMacro() is
3541 // doing when it finds the parameters in the body.
3547 // This macro is defined with parameters, look for \foo, \bar, etc.
3551 // This macro should have parameters, but look for $0, $1, ..., $n too.
3591 if (Parameters[Index].Name == Argument)
3610 Warning(DirectiveLoc, "macro defined with named parameters which are not "
