search for: howtouserangeanalysisinanotherpass

...e config (cmake ../llvm -G "Eclipse CDT4 - Unix Makefiles"), re-open it in Eclipse. 4. Fix some minor issues with range-analysis (some symbols were renamed in newer LLVM releases). 5. Add the necessary code to my own pass, almost verbatim from https://code.google.com/p/range-analysis/wiki/HowToUseRangeAnalysisInAnotherPass. Everything compiles fine, but loading the pass in LLVM gives me the following error: > /opt/llvm/bin/opt: symbol lookup error: ./build/lib/RangeAnalysis.so: undefined symbol: _ZN4llvm13ConstantRangeC1ENS_5APIntES1_ > error: unable to interface with target machine I use LLVM 3.4svn on Ubun...

...e are two other guys working with me on it too. And there are a few users, outside our school that use the pass. If you guys are willing to give our pass a try, we will be more than happy to help you. Notice 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 tha...

...working with me on it too. And there are a few users, > outside our school that use the pass. If you guys are willing to give > our pass a try, we will be more than happy to help you. Notice that we > have put some detailed instructions at > http://code.google.com/p/range-analysis/wiki/HowToUseRangeAnalysisInAnotherPass > about how to use our range analysis. I'd like to look into that, but my schedule to date hasn't permitted me to do so. We have a new person, 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, to...

On 3/29/12 3:59 PM, Victor Campos wrote: > 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

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