search for: getcalledfuntion

...ce too. This will (almost, but see below) give us static guarantees that out-of-tree code remains functional across this transition. Here is my attack plan: I will fire two rounds, - the first will catch all instances of CallInst::get/setOperand(0, ...) and suggest using get/setCalledValue (or getCalledFuntion). - the second will make all low-level operand accessors private in CallInst, and thus give external clients the chance to use *ArgOperand* versions. This will be well-commented in the header, explaining the recommended way of accessing arguments. At this point we will have caught 99%...

...below) give us static guarantees that out-of-tree code remains > functional across this transition. > > Here is my attack plan: > > I will fire two rounds, > - the first will catch all instances of CallInst::get/setOperand(0, ...) > and suggest using get/setCalledValue (or getCalledFuntion). > - the second will make all low-level operand accessors private > in CallInst, and thus give external clients the chance to use > *ArgOperand* versions. This will be well-commented in the > header, explaining the recommended way of accessing > arguments. > > At this...

...t out-of-tree code remains >> functional across this transition. >> >> Here is my attack plan: >> >> I will fire two rounds, >> - the first will catch all instances of CallInst::get/setOperand >> (0, ...) >> and suggest using get/setCalledValue (or getCalledFuntion). >> - the second will make all low-level operand accessors private >> in CallInst, and thus give external clients the chance to use >> *ArgOperand* versions. This will be well-commented in the >> header, explaining the recommended way of accessing >> arguments...

...e below) give us static guarantees that out-of-tree code remains > functional across this transition. > > Here is my attack plan: > > I will fire two rounds, > - the first will catch all instances of CallInst::get/setOperand(0, ...) > and suggest using get/setCalledValue (or getCalledFuntion). > - the second will make all low-level operand accessors private > in CallInst, and thus give external clients the chance to use > *ArgOperand* versions. This will be well-commented in the > header, explaining the recommended way of accessing > arguments. > Stupi...