search for: yapavfunctionpass

...bugpoint.lib and object C:/Users/JDKunk/Documents/Visual Studio 2010/Projects/VSllvm/lib/Debug/bugpoint.exp 2>bugpoint.obj : error LNK2019: unresolved external symbol "class llvm::FunctionPass * __cdecl llvm::createJDKunkRegisterAllocator(void)" (?createJDKunkRegisterAllocator at llvm@@YAPAVFunctionPass at 1@XZ) referenced in function "public: __thiscall `anonymous namespace'::ForcePassLinking::ForcePassLinking(void)" (??0ForcePassLinking@?A0xb2143f5b@@QAE at XZ) 4> Creating library C:/Users/JDKunk/Documents/Visual Studio 2010/Projects/VSllvm/lib/Debug/opt.lib and object C:/U...

...sllvm source code. After the building phase, the vs 2005 dump two errors with the lli and llc. Here is the message: the Error 1549 error LNK2019: unresolved external symbol "class llvm::FunctionPass * __cdecl llvm::createPBQPRegisterAllocator(void)" (?createPBQPRegisterAllocator at llvm@@YAPAVFunctionPass at 1@XZ) referenced in function "public: __thiscall `anonymous namespace'::ForceCodegenLinking::ForceCodegenLinking(void)" (??0ForceCodegenLinking@?A0x75b61eb1@@QAE at XZ) lli.obj Error 1547 error LNK2019: unresolved external symbol "class llvm::FunctionPass * __cdecl llvm::crea...

...bugpoint.lib and object C:/Users/JDKunk/Documents/Visual Studio 2010/Projects/VSllvm/lib/Debug/bugpoint.exp 2>bugpoint.obj : error LNK2019: unresolved external symbol "class llvm::FunctionPass * __cdecl llvm::createJDKunkRegisterAllocator(void)" (?createJDKunkRegisterAllocator at llvm@@YAPAVFunctionPass at 1@XZ) referenced in function "public: __thiscall `anonymous namespace'::ForcePassLinking::ForcePassLinking(void)" (??0ForcePassLinking@?A0xb2143f5b@@QAE at XZ) 4> Creating library C:/Users/JDKunk/Documents/Visual Studio 2010/Projects/VSllvm/lib/Debug/opt.lib and object C:/U...

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

...I succeded to compile almost all the projects, except opt and bugpoint. At these two I had an error: error LNK2019: unresolved 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...

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

...m\win32\\bin\Win32\Debug/opt.lib and object C:\work\s\llvm\win32\\bin\Win32\Debug/opt.exp 1>opt.obj : error LNK2019: unresolved 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...

...> except opt > and bugpoint. At these two I had an error: > > error LNK2019: unresolved external symbol "class llvm::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/LibCallAlia...

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