search for: a0xd1580448

...reateLibCallAliasAnalysisPass(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 can complete llvm to make it a full backend (with the final result...

...s 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 > compiled > out of the box on MSVC Express 2008. We would love t...

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