Displaying 9 results from an estimated 9 matches for "getlazyresolverfunction".
2010 Dec 31
2
[LLVMdev] LLVM on Windows MSVC 10
...ild
cmake .. -G"NMake Makefiles"
nmake
and several link steps fail due to a missing symbol:
> LLVMX86CodeGen.lib(X86JITInfo.cpp.obj) : error LNK2019: unresolved external symbol X86CompilationCallback referenced in function "public: virtual void (__cdecl*__cdecl llvm::X86JITInfo::getLazyResolverFunction(void * (__cdecl*)(void *)))(void)" (?getLazyResolverFunction at X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
What can/should I do?
Thanks!
Ruben
2010 Dec 31
2
[LLVMdev] LLVM on Windows MSVC 10
...> and several link steps fail due to a missing symbol:
>>
>> > LLVMX86CodeGen.lib(X86JITInfo.cpp.obj) : error LNK2019: unresolved
>> > external symbol X86CompilationCallback referenced in function "public:
>> > virtual void (__cdecl*__cdecl llvm::X86JITInfo::getLazyResolverFunction(void
>> > * (__cdecl*)(void *)))(void)"
>> > (?getLazyResolverFunction at X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
>>
>> What can/should I do?
>>
>> Thanks!
>>
>> Ruben
>>
>> _______________________________________________...
2010 Dec 31
0
[LLVMdev] LLVM on Windows MSVC 10
...link steps fail due to a missing symbol:
>>>
>>> > LLVMX86CodeGen.lib(X86JITInfo.cpp.obj) : error LNK2019: unresolved
>>> > external symbol X86CompilationCallback referenced in function "public:
>>> > virtual void (__cdecl*__cdecl llvm::X86JITInfo::getLazyResolverFunction(void
>>> > * (__cdecl*)(void *)))(void)"
>>> > (?getLazyResolverFunction at X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
>>>
>>> What can/should I do?
>
> I'm using SVN Rev. 122644 (trunk), and building for Windows x64 (from
> the MSVC C...
2010 Dec 31
0
[LLVMdev] LLVM on Windows MSVC 10
...les"
> nmake
>
> and several link steps fail due to a missing symbol:
>
> > LLVMX86CodeGen.lib(X86JITInfo.cpp.obj) : error LNK2019: unresolved
> external symbol X86CompilationCallback referenced in function "public:
> virtual void (__cdecl*__cdecl llvm::X86JITInfo::getLazyResolverFunction(void
> * (__cdecl*)(void *)))(void)" (?getLazyResolverFunction at X86JITInfo@llvm@
> @UEAAP6AXXZP6APEAXPEAX at Z@Z)
>
> What can/should I do?
>
> Thanks!
>
> Ruben
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev a...
2010 May 12
2
[LLVMdev] Linking problems with llvm-2.7, release 64b build with vs2010
...C:/llvm-2.7-src/build/lib/Release/Fibonacci.lib and object
C:/llvm-2.7-src/build/lib/Release/Fibonacci.exp
1>LLVMX86CodeGen.lib(X86JITInfo.obj) : error LNK2019: unresolved
external symbol X86CompilationCallback referenced in function "public:
virtual void (__cdecl*__cdecl
llvm::X86JITInfo::getLazyResolverFunction(void * (__cdecl*)(void
*)))(void)" (?getLazyResolverFunction at X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
1>C:\llvm-2.7-src\build\bin\Release\Fibonacci.exe : fatal error
LNK1120: 1 unresolved externals
========== Build: 0 succeeded, 1 failed, 22 up-to-date, 0 skipped ==========
I'...
2010 May 12
0
[LLVMdev] Linking problems with llvm-2.7, release 64b build with vs2010
"Bill O'Hara" <billtohara at gmail.com> writes:
> 1>LLVMX86CodeGen.lib(X86JITInfo.obj) : error LNK2019: unresolved
> external symbol X86CompilationCallback referenced in function "public:
> virtual void (__cdecl*__cdecl
> llvm::X86JITInfo::getLazyResolverFunction(void * (__cdecl*)(void
> *)))(void)" (?getLazyResolverFunction at X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
> 1>C:\llvm-2.7-src\build\bin\Release\Fibonacci.exe : fatal error
> LNK1120: 1 unresolved externals
> ========== Build: 0 succeeded, 1 failed, 22 up-to-date, 0 skippe...
2006 Sep 08
2
[LLVMdev] build broken on linux/amd64
Compiling llvm on a linux/amd64 box produces:
home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function
`_X86CompilationCallback':
(.text+0x316fe): undefined reference to `_X86CompilationCallback2'
/home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function
`llvm::X86JITInfo::getLazyResolverFunction(void* (*)(void*))':
/home/rafael/dev/llvm/cvs/lib/Target/X86/X86JITInfo.cpp:219: undefined
reference to `X86CompilationCallback'
/home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function
`llvm::X86JITInfo::emitFunctionStub(void*,
llvm::MachineCodeEmitter&)':
/home/rafael/dev/llvm...
2010 Feb 16
2
[LLVMdev] Work in progress patch to bug 2606
...the hasAvailableExternallyLinkage
case is dealt with here even though forceEmitFunctionStub(...) would not be entered for this case. I'm forced to
use JITResolver::JITCompilerFn(...) as there is a static relationship between JITResolver and say X86JITInfo. See
implementation of X86JITInfo::getLazyResolverFunction(...) (X86JITInfo.cpp). Should a new JITCompilerFn like
function be created for the purposes of resolving this issue? This would of course require modifications to the
subclasses of TargetJITInfo.
3) JITResolver::JITCompilerFn(...) was modified to no longer exit on being used for non-lazy compi...
2010 Feb 17
0
[LLVMdev] Work in progress patch to bug 2606
...rnallyLinkage
> case is dealt with here even though forceEmitFunctionStub(...) would not
> be entered for this case. I'm forced to
> use JITResolver::JITCompilerFn(...) as there is a static relationship
> between JITResolver and say X86JITInfo. See
> implementation of X86JITInfo::getLazyResolverFunction(...)
> (X86JITInfo.cpp). Should a new JITCompilerFn like
> function be created for the purposes of resolving this issue? This would of
> course require modifications to the
> subclasses of TargetJITInfo.
>
> 3) JITResolver::JITCompilerFn(...) was modified to no longer exit on bein...