search for: analyzefunct

...llvm_function_ret_infer.txt > I would love to ear some feedback, so that this pass can eventually be > merged to the LLVM tree. In particular I'm not sure if there's a better way > to track the possible return values of each function (e.g. is there any code > that I can reuse?) AnalyzeFunction can use BB->getTerminator() rather than iterating over all instructions to find the terminator. After you Analyze all the functions, why not just iterator on the uses of the functions you found you could transform rather than on ever instruction in the module? It seems you should be able to...

Hi, As a follow up of this thread I've made a patch that implements a simple approach to propagate the function return values as described previously. It can transform e.g. the following program: define i32 @f(...) nounwind { (...) %cond = select i1 %tobool, i32 2, i32 3 ; <i32> [#uses=1] ret i32 %cond } define i32 @g(...) nounwind { entry: %call = call i32 (...)* @f() ;