search for: otherargname

...precisely that the $names don't work that way. Your >reasoning would be valid if the $names were function/operator argument >names, like in programming languages where you can pass function >arguments based on their order but also by naming them (e.g. >"functionName(argName=x, otherArgName=y)"). However, this is _not_ how >$names work! > >Their most prominent application is for instruction selection pattern >matching, e.g. taken at random from AMDGPU/SOPInstructions.td: > >def : GCNPat < > (i32 (smax i32:$x, (i32 (ineg i32:$x)))), > (S_ABS_I32 SReg_3...

I included the ability to get/set an operand by name because I thought it would be easier to copy+modify an existing DAG by specifying the name of the operand you want to replace rather than having to remember its position. For example, if you want to replace the first source, isn't it easier to specify $src than remember it's the second operand? Perhaps the people actually coding these

...work that way. Your >> >reasoning would be valid if the $names were function/operator argument >> >names, like in programming languages where you can pass function >> >arguments based on their order but also by naming them (e.g. >> >"functionName(argName=x, otherArgName=y)"). However, this is _not_ how >> >$names work! >> > >> >Their most prominent application is for instruction selection pattern >> >matching, e.g. taken at random from AMDGPU/SOPInstructions.td: >> > >> >def : GCNPat < >> > (i...