search for: _x86targetmachinemodule

...the right direction). >>>> I would have thought that linking with LLVMJIT.lib should suffice... a >>>> VC++ linker issue? >>>> >>>> >>> Try adding this to the link command of your executable: >>> >>> /INCLUDE:_X86TargetMachineModule >>> >>> I should document this somehow. >>> >> Yeah, this is necessary, but not sufficient. I also had to link with >> ExecutionEngineBindings.obj (not JIT.obj as first stated) >> > > So you are using the C bindings. Okay, could someon...

srs <skaflotten at gmail.com> writes: >>>> Try adding this to the link command of your executable: >>>> >>>> /INCLUDE:_X86TargetMachineModule >>>> >>>> I should document this somehow. >>>> >>> Yeah, this is necessary, but not sufficient. I also had to link with >>> ExecutionEngineBindings.obj (not JIT.obj as first stated) >>> >> >> So you are using th...

...to also >> link with JIT.obj (thanks aKor for pointing me in the right direction). >> I would have thought that linking with LLVMJIT.lib should suffice... a >> VC++ linker issue? >> > > Try adding this to the link command of your executable: > > /INCLUDE:_X86TargetMachineModule > > I should document this somehow. > Yeah, this is necessary, but not sufficient. I also had to link with ExecutionEngineBindings.obj (not JIT.obj as first stated) /Stein Roger

...JIT.obj (thanks aKor for pointing me in the right direction). >>> I would have thought that linking with LLVMJIT.lib should suffice... a >>> VC++ linker issue? >>> >> >> Try adding this to the link command of your executable: >> >> /INCLUDE:_X86TargetMachineModule >> >> I should document this somehow. > > Yeah, this is necessary, but not sufficient. I also had to link with > ExecutionEngineBindings.obj (not JIT.obj as first stated) So you are using the C bindings. Okay, could someone advise what to do here? Something like the _X86Targe...

...gt;>> TheExecutionEngine = ExecutionEngine::create(TheModule); >>> >> create returns null, because both JITCtor and InterpCtor are null. >> I found this comment in ExecutionEngine.h >> > > Does it work if you add to the link command > /INCLUDE:_X86TargetMachineModule > > ? > > [snip] I tried linking the tutorial adding that command but JITCtor and InterpCtor are still null, both in debug and release builds. Was by any chance that command meant to be used when building the llvm solution? -------------- next part -------------- An HTML attachment wa...

...). > >>>> I would have thought that linking with LLVMJIT.lib should suffice... a > >>>> VC++ linker issue? > >>>> > >>>> > >>> Try adding this to the link command of your executable: > >>> > >>> /INCLUDE:_X86TargetMachineModule > >>> > >>> I should document this somehow. > >>> > >> Yeah, this is necessary, but not sufficient. I also had to link with > >> ExecutionEngineBindings.obj (not JIT.obj as first stated) > >> > > > > So you are using the C b...

...) when this line is executed >> // Create the JIT. >> TheExecutionEngine = ExecutionEngine::create(TheModule); > create returns null, because both JITCtor and InterpCtor are null. > I found this comment in ExecutionEngine.h Does it work if you add to the link command /INCLUDE:_X86TargetMachineModule ? [snip] -- Oscar

...reate call always returned NULL. The fix was to also > link with JIT.obj (thanks aKor for pointing me in the right direction). > I would have thought that linking with LLVMJIT.lib should suffice... a > VC++ linker issue? Try adding this to the link command of your executable: /INCLUDE:_X86TargetMachineModule I should document this somehow. [snip] -- Oscar

Óscar Fuentes wrote: > srs <skaflotten at gmail.com> writes: > > >>>>> Try adding this to the link command of your executable: >>>>> >>>>> /INCLUDE:_X86TargetMachineModule >>>>> >>>>> I should document this somehow. >>>>> >>>>> >>>> Yeah, this is necessary, but not sufficient. I also had to link with >>>> ExecutionEngineBindings.obj (not JIT.obj as first stated) &gt...

Nicolas, In Visual Studio 2005, you can force the linker to include specific symbols. In your project, under "Configuration Properties/Linker/Input/Force Symbol References", try adding _X86TargetMachineModule. Hope that helps! Stein Pedersen _____ From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Nicolas Capens Sent: 27. mai 2008 00:11 To: 'LLVM Developers Mailing List' Subject: [LLVMdev] X86TargetMachineModule not helping Hi all, After c...

Hi, I'm investigating adding LLVM JIT support to a project of mine, but I'm having issues when trying to compile the Kaleidoscope tutorial* under MSVC 2008. In particular, the problem is that in main() when this line is executed > // Create the JIT. > TheExecutionEngine = ExecutionEngine::create(TheModule); create returns null, because both JITCtor and InterpCtor are null. I

Hi all, While testing my compiler on win32 in JIT mode, I ran into a couple of issues: 1. I linked the compiler with the lib files resulting from the cmake created VS.NET build. While everything built just fine, the ExecutionEngine::create call always returned NULL. The fix was to also link with JIT.obj (thanks aKor for pointing me in the right direction). I would have thought that linking

Hi all, After creating a new LLVM-based project, I faced an odd problem. ExecutionEngine::create always retuned null. After some investigation I found out that it was due to the target architecture not getting registered. I'm using Visual C++ 2005 and in the X86TargetMachine.cpp file an extern variable X86TargetMachineModule is created to 'ensure' that the module is linked in. It

"Viktar Zviarovich" <Viktar.Zviarovich at brunel.ac.uk> writes: [snip] > The function I am trying to call is trivial (took it from the tutorial > just for testing purposes) and has C calling conventions. The > execution engine returned by ExecutionEngine::create is Interpreter. > > Am I doing something wrong or is it a bug? Are you using CMake for generating the

Yes, unfortunately I am using the Visual C++ .NET compiler. Morten Ofstad wrote: > This problem is the motivation for having the _X86TargetMachineModule > symbol in LLVM. I thought this problem was solved by explictly list the object files in the "Additional Dependencies" of the project file? win32/llc/llc.vcproj: AdditionalDependencies="$(SolutionDir)X86\$(IntDir)\X86TargetMachine.obj $(SolutionDir)\CBackend\$(IntDir)\Writer....

Dear llvm-dev, First of all I'd like to thank LLVM developers for doing a great job! I am trying to use LLVM libraries on Windows using Visual Studio environment and everything works very smoothly until it comes to the execution engine. I construct a module and obtain a pointer to the function in it using ExecutionEngine::getPointerToFunction but calling this function (after appropriate

...with CMake was relatively straightforward, and I got a 32-bit x86 build to go through without errors (although I haven't tested it with my application yet). The 64-bit build gets caught up on a few errors. First, all of the executables fail to link because of unresolved symbol errors for "_X86TargetMachineModule" and "_X86AsmPrinterForceLink". I can see where these get set up on the link line in llvm/cmake/modules/LLVMConfig.make file, and I understand why these are required for this build platform. Unfortunately, it looks like the VS 64-bit compiler assigns symbol names differently from th...

I am not sure if my problem is similar to: http://lists.cs.uiuc.edu/pipermail/llvmdev/2003-December/000715.html It seems that the constructor of the static global pass object isn't called: lib/CodeGen/DependenceAnalyzer.cpp: static RegisterAnalysis<DependenceAnalyzer> X("depana", "Dependence Analysis"); I traced into struct RegisterAnalysis ctor, but my pass

...please note that the CMake build system is absolutely unobtrusive wrt current build systems, either the make-based or the MSVC++ project files, and I'm not advocating the deprecation of neither of them. Notes: * MSVC++ users: there is no LLVMX86.o. Link against LLVMX86.lib and add /INCLUDE:_X86TargetMachineModule to your executable's link option. * Right now it ignores most of the examples (only builds Fibonacci). As an exercise, you can add the CMakeLists.txt file to each example directory and make the needed modifications to examples/CMakeLists.txt. * Has no make install nor test. * It is more...

Hola Aaron, Just having that code didn't work since the linker still stripped it out, so I have that function called from the code in the system that actually is being used by our app. Kinda grubby, but I include: #include "llvm/lib/Target/X86/X86TargetMachine.h" Which is in the LLVM lib, not the LLVM inc directory. This little maneuver made our Mac builds really unhappy, so