search for: forcepasslinking

I am writing my register allocator directly in 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 c...

...efore the API change e-mail was released. 1) I created my .cpp file RegAllocJDKunk.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 "...

Jeff Kunkel <jdkunk3 at gmail.com> writes: > I ran cmake to build the visual studio projects. Then I included my > code under the Visual Studio interface, but I placed my code separate > from the CodeGen code. Visual studio was smart enough to compile and > link in my code into the CodeGen library. Thus, I did not need to add > my code into the same directory as the CodeGen

...gt; I am writing my register allocator directly in 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 fil...

I ran cmake to build the visual studio projects. Then I included my code under the Visual Studio interface, but I placed my code separate from the CodeGen code. Visual studio was smart enough to compile and link in my code into the CodeGen library. Thus, I did not need to add my code into the same directory as the CodeGen files, and I did not need to change the CMakeList.txt. The offical name is

...ude/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': /x/grwright/llvm/llvm-2.9/include/llvm/LinkAllPasses.h:152: undefined reference to `llvm::createRelRecoveryPass()' So how do I fix that? Where do I need to be defining this? In addition, when I try to just compile the source files for my pass, I get: llvm[0]: Compiling RelDepInfo.cpp...

...lved external symbol "class llvm::FunctionPass * __cdecl llvm::createLibCallAliasAnalysisPass(class llvm::LibCallInfo *)" (?createLibCallAliasAnalysisPass at llvm@@YAPAVFunctionPass at 1@PAVLibCallInfo at 1@@Z) referenced in function "public: __thiscall `anonymous namespace'::ForcePassLinking::ForcePassLinking(void)" (??0ForcePassLinking@?A0xd1580448@@QAE at XZ) which I wasn't able to fix it. I hope these will be fixed on the final 2.3 release so it can be compiled out of the box on MSVC Express 2008. Now I'm checking on some Windows assemblers and other tools which ca...

...resolved external symbol "class llvm::FunctionPass * __cdecl llvm::createLibCallAliasAnalysisPass(class llvm::LibCallInfo *)" (?createLibCallAliasAnalysisPass at llvm@@YAPAVFunctionPass at 1@PAVLibCallInfo at 1@@Z) referenced in function "public: __thiscall `anonymous namespace'::ForcePassLinking::ForcePassLinking(void)" (??0ForcePassLinking@?A0xe41c907a@@QAE at XZ) 1>C:\work\s\llvm\win32\\bin\Win32\Debug/opt.exe : fatal error LNK1120: 1 unresolved externals It'd be fine for me to use RELEASE_22 tag, but since cfe doesn't have a matching tag, this doesn't quite work. I...

...lvm::FunctionPass * > __cdecl llvm::createLibCallAliasAnalysisPass(class llvm::LibCallInfo > *)" > (? > createLibCallAliasAnalysisPass > @llvm@@YAPAVFunctionPass at 1@PAVLibCallInfo at 1@@Z) > referenced in function "public: __thiscall `anonymous > namespace'::ForcePassLinking::ForcePassLinking(void)" > (??0ForcePassLinking@?A0xd1580448@@QAE at XZ) > > which I wasn't able to fix it. This sounds like lib/Analysis/LibCallAliasAnalysis.cpp needs to be added to the project file. > I hope these will be fixed on the final 2.3 release so it can be &gt...

...my register allocator directly in 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()&quo...

Not that I sympathize with the OP's manners but... Bill Wendling <isanbard at gmail.com> writes: > On May 10, 2008, at 7:55 PM, kr512 wrote: > >> See how gcc is invoked to generate the final executable >> file. This means LLVM is an incomplete backend, >> unfortunately. >> > That's only a convenience. GCC generates assembly code too and calls