Displaying 2 results from an estimated 2 matches for "projectsdisk".
2007 Dec 03
0
[LLVMdev] LLVM footprint
...4, 5.8MB optimized and stripped). Is this normal?
> Am I linking to "too much" or not using the correct link flags?
That is large. I'd suggest using the output of the llvm-config tool to
pass the right options to the linker:
$ llvm-config --libs --ldflags jit native
-L/Volumes/ProjectsDisk/cvs/llvm/Debug/lib -lpthread -lltdl -lm
/Volumes/ProjectsDisk/cvs/llvm/Debug/lib/LLVMPowerPC.o -lLLVMSelectionDAG
-lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa
-lLLVMAnalysis /Volumes/ProjectsDisk/cvs/llvm/Debug/lib/LLVMJIT.o
/Volumes/ProjectsDisk/cvs/llvm/Debug/lib/LLVMExecutio...
2007 Dec 03
2
[LLVMdev] LLVM footprint
-----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?