search for: createxyzpass

...can probably just have them > return IPSCCP instead. I don't necessarily think your conclusion is wrong, but the patch isn't proving what you think it's proving. In fact, the below passes all tests as well. When you call passes through `opt` they don't end up calling through the createXYZPass path. diff --git a/lib/Transforms/IPO/IPConstantPropagation.cpp b/lib/Transforms/IPO/IPConstantPropagation.cpp index b3ee499..8d70b98 100644 --- a/lib/Transforms/IPO/IPConstantPropagation.cpp +++ b/lib/Transforms/IPO/IPConstantPropagation.cpp @@ -253,7 +253,9 @@ char IPCP::ID = 0; INITIALIZE_PASS...

I think this has to do with how the pass manager is populated when we give -O3 vs when we give particular pass names. Some passes have multiple createXYZPass() methods that accept arguments too. These methods call non-default pass constructors, which in turn cause the passes to behave in a different manner. eg: Pass *llvm::createLICMPass() { return new LegacyLICMPass(); } Pass *llvm::createLICMPass(unsigned LicmMssaOptCap, uns...

...wondering if the method is just not optimizable in *any* way or if I am not invoking the stuff correctly. The system setup on a broad scale looks as follows: - custom LLVM-module pass - at some point inside the runOnModule(), it instantiates a PassManager, adds all kinds of optimizations ( PM.add(createXYZPass()) ) and runs them on a provided module. - the module is provided by a bitcode file that is generated with llvm-g++ from a c++-file. There are several problems with the bitcode generated by llvm-g++: - I understand that in LLVM 2.5 all optimizations of gcc are disabled. this leads to horrible c...

The pass is pretty rudimental (as the comment at the top of the file hints), and it seems LLVM already has IPSCCP (which should do a better job at interprocedural constant propagation). I'm also not entirely sure it's used anywhere. Is there any reason to keep it around? Thanks, -- Davide "There are no solved problems; there are only problems that are more or less solved" --

Dear developers, I am trying to reproduce the results of applying opt -O3 to a source file in the form of LLVM IR. I want to get the same IR by manually ordering the passes used by O3 and passing them to opt. To illustrate what I am doing on an example, as an input I use linpack benchmark from the LLVM test suite[1]: 1. First I produce the intermediate representation using clang: clang -O3