search for: llvmbzip2

.../LLVMCBackend.o /home/kh/llvm/obj/Debug/lib/LLVMX86.o /home/kh/llvm/obj/Debug/lib/LLVMSelectionDAG.o /home/kh/llvm/obj/Debug/lib/LLVMCodeGen.o /home/kh/llvm/obj/Debug/lib/LLVMBCReader.o /home/kh/llvm/obj/Debug/lib/LLVMBCWriter.o /home/kh/llvm/obj/Debug/lib/LLVMCore.o /home/kh/llvm/obj/Debug/lib/LLVMbzip2.o --export-dynamic -lLLVMTarget -lLLVMipa -lLLVMTransforms -lLLVMScalarOpts -lLLVMAnalysis -lLLVMTransformUtils -lLLVMSupport -lLLVMSystem -lpthread /usr/lib/libltdl.so -ldl --rpath /home/kh/llvm/obj/Debug/bin -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/lib/gcc/i386-redhat-linux/3.4.3/crte...

...VMIA64.o /usr/build/llvm-2/Debug/lib/LL VMSelectionDAG.o /usr/build/llvm-2/Debug/lib/LLVMCodeGen.o /usr/build/llvm-2/Deb ug/lib/LLVMScalarOpts.o /usr/build/llvm-2/Debug/lib/LLVMBCReader.o /usr/build/ll vm-2/Debug/lib/LLVMBCWriter.o /usr/build/llvm-2/Debug/lib/LLVMCore.o /usr/build/ llvm-2/Debug/lib/LLVMbzip2.o --export-dynamic -lLLVMTarget -lLLVMipa -lLLVMTrans forms -lLLVMAnalysis -lLLVMTransformUtils -lLLVMSupport -lLLVMSystem -lstdc++ -l gcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc /usr/build/llvm-2/Debug/lib/LLVMX86.o(.text+0x30406): In function `_GLOBAL__D__Z N76_GLOBAL__N__usr_src_...

...LVMIA64.o /usr/build/llvm-2/Debug/lib/LLVMSelectionDAG.o /usr/build/l lvm-2/Debug/lib/LLVMCodeGen.o /usr/build/llvm-2/Debug/lib/LLVMScalarOpts.o /usr/ build/llvm-2/Debug/lib/LLVMBCReader.o /usr/build/llvm-2/Debug/lib/LLVMBCWriter.o /usr/build/llvm-2/Debug/lib/LLVMCore.o /usr/build/llvm-2/Debug/lib/LLVMbzip2.o -Wl,--export-dynamic -L/usr/build/llvm-2/Debug/lib -lLLVMTarget -lLLVMipa -lLLV MTransforms -lLLVMAnalysis -lLLVMTransformUtils -lLLVMSupport -lLLVMSystem -L/us r/build/llvm-2/Debug/bin It looks like there is a reference to X86JITInfo but no object file for this is being linked into 'llc...

...j/Debug/lib/LLVMX86.o > /home/kh/llvm/obj/Debug/lib/LLVMSelectionDAG.o > /home/kh/llvm/obj/Debug/lib/LLVMCodeGen.o > /home/kh/llvm/obj/Debug/lib/LLVMBCReader.o > /home/kh/llvm/obj/Debug/lib/LLVMBCWriter.o > /home/kh/llvm/obj/Debug/lib/LLVMCore.o > /home/kh/llvm/obj/Debug/lib/LLVMbzip2.o --export-dynamic -lLLVMTarget > -lLLVMipa -lLLVMTransforms -lLLVMScalarOpts -lLLVMAnalysis > -lLLVMTransformUtils -lLLVMSupport -lLLVMSystem -lpthread /usr/lib/libltdl.so > -ldl --rpath /home/kh/llvm/obj/Debug/bin -lstdc++ -lm -lgcc_s -lgcc -lc > -lgcc_s -lgcc /usr/lib/gcc/i386-re...

Simon Burton <simon at arrowtheory.com> writes: >> There are several possibilities here: either add1 is assigned a NULL >> pointer, or LLVM was unable to use the JIT and generates bytecode >> instead of native code, or invalid native code was generated >> (unlikely). > > Well, it's not NULL: > > (gdb) print add1 > $1 = (int (*)(int)) 0x83e43b8 >

...-config --libnames jit asmparser LLVMAsmParser.o LLVMJIT.o LLVMExecutionEngine.o LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMCore.o libLLVMSupport.a libLLVMSystem.a LLVMbzip2.o Somewhat better is when I use "--libs engine asmparser". It works, and generates an exe around 77Mb. And no complaints when linking. thanks for your help Oscar. Simon. -- Simon Burton, B.Sc. Licensed PO Box 8066 ANU Canberra 2601 Australia Ph. 61 02 6249 6940 http://arrowtheory.co...

...bug/lib/LLVMCodeGen.o c:/projects/build/MinGW/llvm-1-1/Debug/lib/LLVMScalarOpts.o c:/projects/build/MinGW/llvm-1-1/Debug/lib/LLVMBCReader.o c:/projects/build/MinGW/llvm-1-1/Debug/lib/LLVMBCWriter.o c:/projects/build/MinGW/llvm-1-1/Debug/lib/LLVMCore.o c:/projects/build/MinGW/llvm-1-1/Debug/lib/LLVMbzip2.o --export-dynamic -lLLVMTarget -lLLVMipa -lLLVMTransforms -lLLVMAnalysis -lLLVMTransformUtils -lLLVMSupport -lLLVMSystem -limagehlp -lpsapi -lstdc++ -lmingw32 -lgcc -lmoldname -lmingwex -lmsvcrt -luser32 -lkernel32 -ladvapi32 -lshell32 -lmingw32 -lgcc -lmoldname -lmingwex -lmsvcrt c:/MinGW/bi...

On Fri, 14 Apr 2006 03:25:39 +0200 Oscar Fuentes <oscarfv at telefonica.net> wrote: ... > Simon, > > With a fresh CVS checkout, I've tried your test case on Windows/VC++ > and it works ok. Too bad that I have not access to a Linux machine > right now. I'll like to see what's wrong with your test case. > > What you get from running the test case under gdb

On Fri, 11 Mar 2005, Marc Ordinas i Llopis wrote: > Sorry if this is obvious. > I'm trying to link LLVM-generated code with LLVM itself, and don't know how > to do it. Just as a little test, I've tried compiling the example > HowToUseJIT.cpp using llvm-g++, but I get tons of errors. > > Is there an easy way of doing this? Has anyone tried it before? What sort of

I did not report this first error earlier as I thought it trivial. Basically it looks like something odd is happening with the configuration and 'include/llvm/config/config.h' Getting this error on building the tools on a fresh Cygwin install and update :- $ make tools-only make[1]: Entering directory `/usr/build/llvm/lib/System' llvm[1]: Compiling Path.cpp for Debug build In file

Hi These are: ======================== llvm[2]: Linking Release Object Library LLVMbzip2.o gmake[2]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support/bzip2' gmake[1]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support' gmake[1]: Entering directory `/homes/myuser/LLVM/llvmobj/utils' gmake[2]: Entering directory `/homes/myuser/LLVM/llvmobj/utils/Burg' llvm...

Hi all, Sorry if this is obvious. I'm trying to link LLVM-generated code with LLVM itself, and don't know how to do it. Just as a little test, I've tried compiling the example HowToUseJIT.cpp using llvm-g++, but I get tons of errors. Is there an easy way of doing this? Has anyone tried it before? Thanks, Marc Ordinas i Llopis | Tragnarion Studios

...endif LLVMLIBS = -L$(LLVMLIBPATH) $(LLVMLIBPATH)/$(LLVMTARGETOBJ) -lLLVMScalarOpts \ -lLLVMTransformUtils -lLLVMAnalysis \ $(LLVMLIBPATH)/LLVMSelectionDAG.o $(LLVMLIBPATH)/LLVMCodeGen.o \ -lLLVMTarget $(LLVMLIBPATH)/LLVMBCWriter.o \ $(LLVMLIBPATH)/LLVMbzip2.o \ $(LLVMLIBPATH)/LLVMCore.o -lLLVMSupport -lLLVMSystem uhm... *yuck*. > Gnome (and many other Unix projects with massively ugly dependencies) can be > linked trivially using a "foo-config" script. If LLVM had something similar, > it might save new LLVM develope...

...ored. gccld: warning: File of unknown type '/home/marc/code/llvm/build/Debug/lib/LLVMBCReader.o' ignored. gccld: warning: File of unknown type '/home/marc/code/llvm/build/Debug/lib/LLVMCore.o' ignored. gccld: warning: File of unknown type '/home/marc/code/llvm/build/Debug/lib/LLVMbzip2.o' ignored. gccld: warning: File of unknown type '/home/marc/code/llvm/tests/sample/Debug/bin' ignored. and the linker goes into an infinite loop, never returning to the command line. Finally, I tried first generating the .o (bytecode) file, and then linking got me the same result....

On Mar 10, 2006, at 2:57 PM, Martin Pärtel wrote: > I'm currently using the "make install"-ed version of LLVM in an > autoconf/automake project. Setting it up wasn't that bad really. > The .a > libraries can be statically linked with the -l flag and .o > libraries are > simply linked in as normal object files (without -l). All the > libraries got >

...se/lib/LLVMCBackend.o -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMAnalysis /home/ahs3/tmp/llvm-1.7/llvm/Release/lib/LLVMSelectionDAG.o /home/ahs3/tmp/llvm-1.7/llvm/Release/lib/LLVMCodeGen.o -lLLVMTarget /home/ahs3/tmp/llvm-1.7/llvm/Release/lib/LLVMBCWriter.o /home/ahs3/tmp/llvm-1.7/llvm/Release/lib/LLVMbzip2.o /home/ahs3/tmp/llvm-1.7/llvm/Release/lib/LLVMCore.o -lLLVMSupport -lLLVMSystem /home/ahs3/tmp/llvm-1.7/llvm/Release/lib/LLVMCBackend.o: In function `__static_initialization_and_destruction_0(int, int)': Writer.cpp:(.text+0x379): undefined reference to `llvm::FindUsedTypes::stub()' /home/...

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron