Displaying 4 results from an estimated 4 matches for "pavlibcallinfo".
2008 May 11
1
[LLVMdev] building llvm on Windows
...lmost 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 be compiled
out of...
2008 May 17
1
[LLVMdev] VS build is broken again
...g/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'd be fine for me...
2008 May 12
0
[LLVMdev] building llvm on Windows
...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/LibCallAliasAnalysis.cpp needs...
2008 May 11
9
[LLVMdev] Preferring to use GCC instead of LLVM
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