similar to: [LLVMdev] Compiled Code size

Hello all, I'm trying to bring an LLVM-based project that is working on Linux up on Win32. I am having problems with llvm::ExecutionEngine::create returning a NULL. I traced it to these lines: // Unless the interpreter was explicitly selected, try making a JIT. if (!ForceInterpreter && JITCtor) EE = JITCtor(MP, ErrorStr); // If we can't make a JIT, make an

On Thu, Jul 30, 2009 at 11:03 PM, james northrup<northrup.james at gmail.com> wrote: > CC="p llvm-gcc-4.2 `llvm-config --cflags` -march=i386  --emit-llvm -O0 >  -c -I$PLAT/include -I$ROOT/include -I$ROOT/utils/    include" > LD="p llvm-ld `llvm-config --ldflags --libs all  `" > AR="p llvm-ar crvs" Using llvm-ar+llvm-ld is likely to give you bad

"Aaron Dwyer" <llvmification at gmail.com> writes: [snip] > JITCtor and InterpCtor are both NULL, so it's obvious why I'm getting > back a NULL execution engine. I am pretty sure it's because I'm > missing a few llvm .lib or .obj files. What is the set of llvm object > files needed at link time for Win32 on X86 JIT? This is what I use on MinGW. It

> I don't know anything about Solaris, but your paste doesn't actually > contain any errors, just warnings (unless I'm reading "ld: warning: > relocation error:" wrong). It might help to run make without -j until > it fails, and then use `make VERBOSE=1` to print the exact commands > it's running. Sorry. There was so much output I wasn't sure how much

Hi, I tried to implement an 'llc'-like tool in my project to manage different passes and a target machine. I use given llvm project structure to avoid problems but I have a link problem and don't know how to solve it: The target machine uses 'FindUsedTypes' pass and when I try to use my target machine in the tool I got "Undefined symbols:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is the expected footprint of a tool using the LLVM JIT? I have created a simple project that uses the LLVM C++ API to JIT calls to XPCOM method signature... it works well, but the component DLL is very large (Linux x86-74, 5.8MB optimized and stripped). Is this normal? Am I linking to "too much" or not using the correct link flags?

I ran with VERBOSE=1 and see: g++ -I/home/neale/LLVM/llvm/include -I/home/neale/LLVM/llvm/tools/llc -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g -fno-exceptions -fPIC -Woverloaded-virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused -Wno-unused-parameter -g -Wl,-R -Wl,/home/neale/LLVM/llvm/Debug/bin -Wl,-export-dynamic

Hello, can anyone help me calling native functions from LLVM-Bytecode functions run in the JIT? I have a program which creates an LLVM execution engine and adds modules and functions to it on the fly. I need to call some native functions of my program from bytecode functions which causes some troubles as it appears not to be documented. My test scenario works like the following: I have

hello, I'm attempting to build the inferno source tree using either of native LTO or jit'd bins and having no obvious luck. im using macports (current as of this email) llvm-2.5 and llvm-gcc on a macbook pro (x86) following the inferno directions verbatim will use 'cc' as the compiler and just works. the build tools are different from the naive build tools as follows:

Dear Nico, I believe you need to add LLVMipa to the list of libraries to link into your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if you added it to LINK_COMPONENTS. -- John T. Nico wrote: > Hi, > > I tried to implement an 'llc'-like tool in my project to manage > different passes and a

Hello, Neale > -lLLVMBitReader /home/neale/LLVM/llvm/Debug/lib/LLVMCBackend.o > -lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis > /home/neale/LLVM/llvm/Debug/lib/LLVMCppBackend.o -lLLVMTarget -lLLVMCore > -lLLVMSupport -lLLVMSystem -lpthread -ldl -lm -lelf It seems, that you did not specify any single backend except C. Please do so. > So it

On Thu, Apr 29, 2010 at 6:31 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Wed, Apr 28, 2010 at 10:48 AM, Yuri <yuri at tsoft.com> wrote: >> Jeffrey Yasskin wrote: >>> >>> We currently use two different techniques to get whole libraries >>> included into the .so. On Linux (gnu ld and gold), we pass >>> --whole-archive, while on

-------------------------------------------------- From: "Óscar Fuentes" <ofv at wanadoo.es> Sent: Friday, December 11, 2009 4:32 PM To: <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] Rebuilding LLVM libraries with LLVM-GCC on Windows > > You are working with an assembler file. Why? Here is the build process I'm using for my project: I have a program written in

"Michael Ness" <mike at liquido2.com> writes: [snip] > I then used both of these builds to attempt to assemble and link my > project with llvm-g++: > > $ llvm-g++ out.s -o out.exe `llvm-config --ldflags --libs x86 core > system support` > > gave me the errors found in the attached file "errors_gcc.txt". And > > $ llvm-g++ out.s -o out.exe

Am 02.10.2009 um 21:07 schrieb Ronald Pijnacker: > I had a close look at the link line, and -lpsapi is specified before > -lLLVMSystem (which is giving the error). > When I put -lpsapi after -lLLVMSystem, it links ok. I commited a fix for this problem and a modified version of Jay's patch here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090928/088265.html I

Hello, Neale > These entry points are in modules that have been compiled and placed into an > archive. (e.g. llvm::createBURRListDAGScheduler is in ScheduleDAGRRList.cpp > whose object is placed in ./Debug/lib/libLLVMSelectionDAG.a). > > I'm sure I've missed a configuration option or something trivial like that > but my newbie brain can't determine what it is. make

I'm linking a program (my ellsif driver) that basically brings in most of the LLVM stuff: bitcode reading, optimizations, linking, and target code generation. All of a sudden, I'm getting the following when I run: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions -O5 <premain>: CommandLine Error: Argument 'machine-licm' defined more than once!

Hi all, (Sorry if the answer to this is obvious - and thanks in advance~) Short version: linker error of _backtrace from LLVMSystem.a building a dynamic library embedding LLVM/clang, both against the OSX 10.4 sdk. Long version: I've just tried rebuilding my project using the 2.6 release, using the following commands to try and force LLVM to build against the OSX 10.4 sdk (I am

Beckert Frey <beckert.frey at yahoo.com> writes: [snip] > Is InstCombine required for lli? Yes: $ llvm-config --libs mcjit jit interpreter nativecodegen bitreader asmparser selectiondag -lLLVMAsmParser -lLLVMBitReader -lLLVMX86CodeGen -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMMCParser -lLLVMInterpreter -lLLVMJIT

Hello everybody, after moving from OS X to Linux build llvm with asan enabled (I also updated to trunk, but not sure if that's related). However, it's totally possible that I missed a step that I took back when I set this up for me, so I might be doing something very stupid. Anyway, I'm configuring LLVM with ../configure --prefix=/home/kfischer/julia/usr --build=x86_64-pc-linux-gnu