search for: modulemak

...iculties. I started with the 'LLVM Project Guide', but got hung up in the complexities of configure.ac. I'm now using llvm-config to provide the linker directives, but this results in undefined references: $ llvm-g++ `$HOME/local/bin/llvm-config --cppflags --ldflags --libs bitwriter` ModuleMaker.cpp Yields: /tmp/ccjh9OY1.o: In function `main': ModuleMaker.cpp:(.text+0x13): undefined reference to `llvm::LLVMContext::LLVMContext()' ModuleMaker.cpp:(.text+0x66): undefined reference to `llvm::Module::Module(llvm::StringRef, llvm::LLVMContext&)' ModuleMaker.cpp:(.text+0x7a):...

...an, e0082888 at e0082888-laptop:~$ local/bin/llvm-config --libs bitwriter -lLLVMBitWriter -lLLVMCore -lLLVMSupport -lLLVMSystem I verified it's pulling from the right library directory, because if I hide libLLVMCore.a from view and I get: e0082888 at e0082888-laptop:~/projects/llvm-hs/tools/ModuleMaker$ g++ `$HOME/local/bin/llvm-config --cppflags --cxxflags --ldflags --libs bitwriter` ModuleMaker.cpp /usr/bin/ld: cannot find -lLLVMCore collect2: ld returned 1 exit status And libLLVMCore.a contains at least something related to LLVMContext: e0082888 at e0082888-laptop:~/local/lib$ objdump -h l...

...'LLVM Project Guide', but got hung > up in the complexities of configure.ac. I'm now using llvm-config to > provide the linker directives, but this results in undefined > references: > > $ llvm-g++ `$HOME/local/bin/llvm-config --cppflags --ldflags --libs > bitwriter` ModuleMaker.cpp > > Yields: > > /tmp/ccjh9OY1.o: In function `main': > ModuleMaker.cpp:(.text+0x13): undefined reference to > `llvm::LLVMContext::LLVMContext()' > ModuleMaker.cpp:(.text+0x66): undefined reference to > `llvm::Module::Module(llvm::StringRef, llvm::LLVMContext&am...

Hi all, I think there is still too few docs/samples for those, who'd like to write JIT-based interpreters. Today, the real examples to learn from are rather: - lli.cpp - ModuleMaker.cpp - Stacker which is still unfortunatelly not that much about JITing :( Well, what I am going to sell: What about very small JIT-based example similar to ModuleMaker? I mean example, where, say, two simple functions are created, inserted to a Module/BasicBlock, then executed via JIT an...

...s/Instrumentation/ProfilePaths/Debug ? llvm/lib/Transforms/Instrumentation/ProfilePaths/Depend ? llvm/lib/Transforms/Scalar/Debug ? llvm/lib/Transforms/Scalar/Depend ? llvm/lib/Transforms/Utils/Debug ? llvm/lib/Transforms/Utils/Depend ? llvm/lib/VMCore/Debug ? llvm/lib/VMCore/Depend ? llvm/projects/ModuleMaker/Makefile.common ? llvm/projects/ModuleMaker/config.log ? llvm/projects/ModuleMaker/config.status ? llvm/projects/ModuleMaker/tools/Debug ? llvm/projects/ModuleMaker/tools/ModuleMaker/Debug ? llvm/projects/ModuleMaker/tools/ModuleMaker/Depend ? llvm/projects/Stacker/lib/compiler/Debug ? llvm/proje...

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In

...t; `/home/fpeng/llvm/Debug/examples/HowToUseJIT'. > make[2]: Target `all' not remade because of errors. > make[2]: Leaving directory `/home/fpeng/llvm/examples/HowToUseJIT' > make[1]: *** [HowToUseJIT/.makeall] Error 2 > make[2]: Entering directory `/home/fpeng/llvm/examples/ModuleMaker' > llvm[2]: Compiling ModuleMaker.cpp for Debug build > make[2]: *** No rule to make target > `/home/fpeng/llvm/Debug/lib/LLVMCore.o', needed by > `/home/fpeng/llvm/Debug/examples/ModuleMaker'. > make[2]: Target `all' not remade because of errors. > make[2]: Le...

Ok, that makes sense :). , Tobias On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > > return *FieldPtr; > > > } > > > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > > cases? > > For the field pointer, one

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > return *FieldPtr; > > } > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > cases? For the field pointer, one could use the getelementptr instruction: %pairty = { sbyte, sbyte, int* } %pairPtr = ... %fieldptr = getelementptr

Checking out LLVM from svn and building, I get: llvm[2]: Linking Release executable ModuleMaker (without symbols) /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMX86.o(.eh_frame); no .eh_fr ame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n o .eh_frame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/li...

...s/Instrumentation/ProfilePaths/Debug ? llvm/lib/Transforms/Instrumentation/ProfilePaths/Depend ? llvm/lib/Transforms/Scalar/Debug ? llvm/lib/Transforms/Scalar/Depend ? llvm/lib/Transforms/Utils/Debug ? llvm/lib/Transforms/Utils/Depend ? llvm/lib/VMCore/Debug ? llvm/lib/VMCore/Depend ? llvm/projects/ModuleMaker/Makefile.common ? llvm/projects/ModuleMaker/config.log ? llvm/projects/ModuleMaker/config.status ? llvm/projects/ModuleMaker/tools/Debug ? llvm/projects/ModuleMaker/tools/ModuleMaker/Debug ? llvm/projects/ModuleMaker/tools/ModuleMaker/Depend ? llvm/projects/Stacker/lib/compiler/Debug ? llvm/proje...

...\Target\X86\Disassembler\LLVMX86Disassembler.vcproj" LLVMX86Info, "lib\Target\X86\TargetInfo\LLVMX86Info.vcproj" LLVMipa, "lib\Analysis\IPA\LLVMipa.vcproj" LLVMipo, "lib\Transforms\IPO\LLVMipo.vcproj" ModuleMaker, "examples\ModuleMaker\ModuleMaker.vcproj" X86CodeGenTable_gen, "lib\Target\X86\X86CodeGenTable_gen.vcproj" ZERO_CHECK, ".\ZERO_CHECK.vcproj" bugpoint, "tools\bugpoint\bugpoint.vcproj" check, &...

...; > program with the LLVM and then load the bytecode in memory and finally > > dump some kind of text/XML representation which I will use to understand > > the set of classes needed to dynamically create the sample program > > Check out these directories: > > examples/ModuleMaker/ : Builds a module from scratch > > examples/Fibonacci/ > examples/HowToUseJIT/ : Examples building a module and JIT'ing them. > > -Chris > > -- > http://nondot.org/sabre/ > http://llvm.cs.uiuc.edu/ > > _______________________________________________ >...

Hi Andrew, > Checking out LLVM from svn and building, I get: > > llvm[2]: Linking Release executable ModuleMaker (without symbols) > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMX86.o(.eh_frame); no .eh_fr > ame_hdr table will be created. > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n > o .eh_frame_hdr table will be created. > /usr/bin/ld: error in...

...ve it ready? :) Reid. On Sun, 2004-08-08 at 13:11, Valery A.Khamenya wrote: > Hi all, > > I think there is still too few docs/samples for those, > who'd like to write JIT-based interpreters. > > Today, the real examples to learn from are rather: > > - lli.cpp > - ModuleMaker.cpp > - Stacker > > which is still unfortunatelly not that much > about JITing :( > > Well, what I am going to sell: > > What about very small JIT-based example similar > to ModuleMaker? > > I mean example, where, say, two simple functions are > created...

Folks, The projects cleanup has been completed. The "ModuleMaker" project is now in projects/SmallExamples/ModuleMaker. Additionally there are two new programs in SmallExamples contributed by Valery Khamenya: Fibonacci and HowToUseJIT. Thanks Valery! You should "cvs update -PdR" in the projects directory to get the changes. Thanks, Reid.

...You can > only build one program per directory. Were you suggesting that you wanted me to > move the entire directories under a "small examples" directory? You're right. The simples way to do this would be to have: projects/ SmallExamples/ ModuleMaker/ HowToUseTheJIT/ FibBuilder/ etc. Each subsubdir would have a makefile and a .cpp file. -Chris > Chris Lattner wrote: > > > On Tue, 17 Aug 2004, Reid Spencer wrote: > > > > > >>That's pretty cute actually....

...\Target\X86\Disassembler\LLVMX86Disassembler.vcproj" LLVMX86Info, "lib\Target\X86\TargetInfo\LLVMX86Info.vcproj" LLVMipa, "lib\Analysis\IPA\LLVMipa.vcproj" LLVMipo, "lib\Transforms\IPO\LLVMipo.vcproj" ModuleMaker, "examples\ModuleMaker\ModuleMaker.vcproj" X86CodeGenTable_gen, "lib\Target\X86\X86CodeGenTable_gen.vcproj" ZERO_CHECK, ".\ZERO_CHECK.vcproj" bugpoint, "tools\bugpoint\bugpoint.vcproj" check, &...

On Tue, 17 Aug 2004, Reid Spencer wrote: > That's pretty cute actually. Do you want this "brilliant" :) example in the cvs > repository? I'd be happy to put it in. Here's an idea: how about we take the ModuleMaker, Valery's previous example, and this one and put them all in one "small examples" project? -Chris > Valery A.Khamenya wrote: > > > Hi LLVMers, > > > > the example attached I have used to prove that JIT and some visible > > optimizations are really...

...didn't like. I remember SourceForge's compile farm has an OpenBSD x86 machine so thought I'd give it a go with a recent CVS check-out. $ ./configure configure: WARNING: Unknown project (HowToUseJIT) won't be configured automatically configure: WARNING: Unknown project (ModuleMaker) won't be configured automatically configure: WARNING: Unknown project (SmallExamples) won't be configured automatically checking build system type... i386-unknown-openbsd3.8 checking host system type... i386-unknown-openbsd3.8 checking target system type... i386-unknown-o...