search for: lazyinfo

...that we have put some detailed instructions at http://code.google.com/p/range-analysis/wiki/HowToUseRangeAnalysisInAnotherPass about how to use our range analysis. > The idea of integrating your pass as a lazy value pass sounds good. The > question I have is what optimizations benefit from LazyInfo? I only see > one or two transforms that use it in LLVM 3.0. Yes, I do not think there are many optimizations that use LazyInfo so far. But maybe, backed by a more aggressive analysis, LazyInfo will be more effective. I can implement dead-code elimination based on value ranges, and I think it...

...that looks for icmp instructions and uses your analysis to change them to true/false when possible. SCCP, ADCE, and other optimizations would then take care of the rest. The idea of integrating your pass as a lazy value pass sounds good. The question I have is what optimizations benefit from LazyInfo? I only see one or two transforms that use it in LLVM 3.0. > > I would like to hear from you what you think about this Summer of Code > project. If you think it could be interesting, I will write a proposal > richer in details. My interest in range analysis is for using it with SAFE...

Dear LLVMers, I have been working on Douglas's range analysis, and today, after toiling with it for two years, we have a very mature and robust implementation, which is publicly available at http://code.google.com/p/range-analysis/. We can, at this point, perform range analysis on very large benchmarks in a few seconds. To give you an idea, we take less than 10 seconds to globally analyze

...son, though, that might be able to look into that in the coming months. It seems Raphael Ernani Rodrigues may be interested in working on it, too. > > > The idea of integrating your pass as a lazy value pass sounds good. The > > question I have is what optimizations benefit from LazyInfo? I only see > > one or two transforms that use it in LLVM 3.0. > > Yes, I do not think there are many optimizations that use LazyInfo so > far. But maybe, backed by a more aggressive analysis, LazyInfo will be > more effective. I can implement dead-code elimination based on value...