search for: setcalledvalue

...stination of those call instructions to my own library functions that happens to have the same arguments and return types of the original callee. It works perfectly for direct calls using setCalledFunction(). But when the function call is indirect, is there a way to set the callee? Something like setCalledValue()? How do I achieve this? Any help will be appreciated, thanks a lot! -- Arnamoy Bhattacharyya Athabasca Hall 143 Department of Computing Science - University of Alberta Edmonton, Alberta, Canada, T6G 2E8 587-710-7073

...high-level interface 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...

...lmost, 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 > argument...

...atic 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...

...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 > argu...