search for: linkallpasses

All the functions in LinkAllPasses.h are passes. I am not sure whether it takes inline functions. I added createPostDomTree() to LinkAllPasses.h but I get the same error. I wonder whether it was even worth it making the functions inline for PostDominators.h. George On Tue, Aug 21, 2012 at 9:05 AM, Tobias Grosser <tobias at gros...

I have done that. I have defined createMyAnaPass() in Passes.h and it is defined in MyAna.cpp and used in LinkAllPasses.h But still the error : /home/ambika/llvm/llvm-obj/tools/opt/Release/opt.o: In function `global constructors keyed to opt.cpp': opt.cpp:(.text+0x1e89): undefined reference to `llvm::createMyAnaPass()' I dont understand whats the problem. Jianzhou Zhao wrote: > On Tue, Feb 23, 2010...

...static RegisterPass<MyAna> X("my-aa","My Analysis"); >> static RegisterAnalysisGroup<AliasAnalysis> Y(X); >> >> ModulePass *llvm::createMyAnaPass() { return new MyAna(); } >> >> >> I also included createMyAnaPass() in Passes.h and LinkAllPasses.h >> But when I do make I get the following error : >> >> /home/ambika/llvm/llvm-obj/tools/opt/Release/opt.o: In function `global >> constructors keyed to opt.cpp': >> opt.cpp:(.text+0x1e89): undefined reference to `llvm::createMyAnaPass()' >> >> &g...

...on this bug for a while. I inserted a pass under lib/Transforms/mypass directory, registered it with INITIALIZE_PASS and defined createMyPass in the pass. Also I added file mypass.h in include/llvm/Transforms/ to expose the accessor functions that expose my passes. Entries are added in include/llvm/LinkAllPasses.h to force pass linking. The archive files of my passes are added to LINK_COMPONENTS in the Makefiles for opt and clang. However, the passes are still not statically linked. Is there a way to statically link a pass into clang? If possible, how do turn on and off my passes with command line options?...

...side ‘llvm’ > > but I can find no place to declare it. > Where should I do it. We can do what scalar optimizations do. All scalar passes are declared in include/llvm/Transforms/Scalar.h and include/llvm-c/Transforms/Scalar.h, defined in lib/Transforms/Scalar.cpp, and used in include/llvm/LinkAllPasses.h. Jianzhou > > > John Criswell wrote: >> ambika at cse.iitb.ac.in wrote: >>> Hi, >>> >>> I am trying to add a pass inn LLVM, and I actually want to add it in >>> source code, not just directly into object code. >>> >>> For that...

...compile llvm in release mode, the problem goes away! I don't understand? > > probably the function defined in the header is inlined into every function that > calls it when optimization is turned on, but not when optimization is turned > off. You can try to add it into include/llvm/LinkAllPasses.h. There are already a couple of other functions that have been put here to not be eliminated. BTW, is there no better way to mark a function as used externally? Tobi

...covery, "relRecovery", "Reliability transformation for lightweight recovery", false, false) However, as my pass is external the rest of llvm (and is compiled separately from the main llvm source), I am having trouble getting this to work. I was told to also modify include/llvm/LinkAllPasses.h to add a call to (void) llvm::createRelRecoveryPass(); which I have done, but when I go to my main llvm-obj directory to build llvm so that the call is valid when I actually compile my pass files, I get: /x/grwright/llvm/llvm-obj/tools/opt/Debug+Asserts/opt.o: In function `ForcePassLinking':...

Hi George, > When I compile llvm in release mode, the problem goes away! I don't understand? probably the function defined in the header is inlined into every function that calls it when optimization is turned on, but not when optimization is turned off. Ciao, Duncan.

Ah, I was missing that include/llvm/LinkAllPasses.h change. Thanks! Now I have it working, except for the fact that it doesn't seem to generate fresh names for things. Or if it does, they're the empty string (I suspect it is the latter, since when I create the new instruction the empty string is passed in for the name of the instruction)...

On Wed, 4 Jul 2007, Ben Chambers wrote: > Ah, I was missing that include/llvm/LinkAllPasses.h change. Thanks! > Now I have it working, except for the fact that it doesn't seem to > generate fresh names for things. Or if it does, they're the empty > string (I suspect it is the latter, since when I create the new > instruction the empty string is passed in for the name...

...objdir and running make again. Re-configuring LLVM also does > > It sounds like the dependencies for your pass are not correct. Where > did you put it in the LLVM tree and how did you change the Makefiles? One new .cpp file in lib/Transforms/IPO + RegisterPass<> + mention pass in LinkAllPasses.h; no changes in makefiles. > > not trigger rebuild when running make, e.g. after initial 'configure > > --enable-targets=x86' I've managed to get C backend only after removing > > objdir and re-configuring (was too lazy to check if 'make clean' is > > s...

...(llvm-2.6/lib/ana/MyAna.cpp) char MyAna::ID = 0; static RegisterPass<MyAna> X("my-aa","My Analysis"); static RegisterAnalysisGroup<AliasAnalysis> Y(X); ModulePass *llvm::createMyAnaPass() { return new MyAna(); } I also included createMyAnaPass() in Passes.h and LinkAllPasses.h But when I do make I get the following error : /home/ambika/llvm/llvm-obj/tools/opt/Release/opt.o: In function `global constructors keyed to opt.cpp': opt.cpp:(.text+0x1e89): undefined reference to `llvm::createMyAnaPass()' Am I missing out something. Please help me. thanks and regar...

...ad > Release/lib/LLVMLowerConstExps --help it shows up. Ok. Now I run > make install. Now if I run opt -load Release/lib/LLVMLowerConstExps I > get an error message. Specifically, I get: I'd suggest adding it back to the scalar directory. Then make sure to add it to include/llvm/LinkAllPasses.h -Chris > Error opening 'lib/LLVMLowerConst': Can't open :lib/LLVMLowerConst: > dlopen(lib/LLVMLowerConst.0.dylib, 9): Symbol not found: > __ZN4llvm12FunctionPass11runOnModuleERNS_6ModuleE > Referenced from: > /Users/benchambers/Documents/research/llvm/llvm-2.0/Releas...

...the LLVM tree, and I am having trouble linking my project on windows msvc 10.0 compiler. The error are below, but let me say what I have changed. 1. I added "(void) llvm::createJDKunkRegisterAllocator();" to the struct ForcePassLinking::ForcePassLinking() method in "llvm\include\llvm\LinkAllPasses.h" 2. I added "FunctionPass* createJDKunkRegisterAllocator();" to header "llvm\CodeGen\Passes.h." 3. I implemented "FunctionPass* createJDKunkRegisterAllocator()" in my cpp file. I know the api change said some items were changed, and it has worked until the api...

...> definition of the pass in some other file also. I observed how gvn pre > pass is added to the pass list. I had followed the same way, but failed. > Cna you kindly tell what needs to be done in this regard? What's the error you're getting? There are two other files, include/llvm/LinkAllPasses.h and include/llvm/Transforms/Scalar.h which I think you would've already added your pass to if "opt -your-pre-pass" was working, but I'll mention them anyway. Nick > On 23 August 2010 00:13, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wr...

Ok. So I took the source code from 1.5 for the LowerConstantExprs pass and (hopefully) corrected all the bitrot. It now compiles. But opt doesn't see it (when I run Release/bin/opt --help it doesn't show up). So, I copy the Transform/Hello directory and compile it as a dynamically loaded pass. When I run Release/bin/opt -load Release/lib/LLVMLowerConstExps --help it shows up. Ok.

...r this pass into the PassRegistry Then, for a built-into bytecode pass, task 1(declaration of the creator) should be done in Scalar.h; task 2(implementation of the creator) should be done the related mypass.cpp file; task 3(instantiation of the pass class) should be done in LinkAllPasses.h; task 4(registration of the pass into the PassRegistry) should be done by INITIALIZE_PASS class LiveVariables : public MachineFunctionPass is a case of point. For a built-into codegen/MachineCode pass, task 1 should be done in Passes.h; task 2 should be done in the relate...

...gAllocJDKunk.cpp in llvm/lib/CodeGen/ directory. 2) I updated the CMakeList.txt in the directory llvm/lib/CodeGen/ to include RegAllocJDKunk.cpp. 3) I added "(void) llvm::createJDKunkRegisterAllocator();" to the struct ForcePassLinking::ForcePassLinking() method in "llvm\include\llvm\LinkAllPasses.h" 4) I added "FunctionPass* createJDKunkRegisterAllocator();" to header "llvm\CodeGen\Passes.h." 5) I implemented "FunctionPass* createJDKunkRegisterAllocator()" in my cpp file. 6) I added "initializeRAJDKunk(Registry);" to llvm/lib/CodeGen/CodeGen.cpp...

...on. > > > > Running `ltrace` surfaced a number of `getenv("bar")` calls coming from > > llvm. It turns out these are not "real" `getenv` calls, but are an > > optimization "do nothing" escape hatch which have been in > > `llvm/include/llvm/LinkAllPasses.h` [for over 15years](1) - apparently > > as a way to prevent the compiler eliminating symbol references to > > optimization pass initialization functions. I took a look at the code > > and couldn't really work out what issue is being solved as the commit > > messages fr...

...nuary 2010 12:18, Gregory Petrosyan wrote: > > It sounds like the dependencies for your pass are not correct. Where > > did you put it in the LLVM tree and how did you change the Makefiles? > > One new .cpp file in lib/Transforms/IPO + RegisterPass<> + mention pass in > LinkAllPasses.h; no changes in makefiles. Hmm, that should certainly work. What file are you touching that make doesn't seem to pick up? > > A non-build after reconfigure is not really a problem. If nothing in > > the configuration has changed configure is smart enough not to update > >...