similar to: [LLVMdev] using dynamic libraries from bytecode?

Mike Stump wrote: >> Is it possible to use dynamic library (*.so *.dll) from bytecode? >> If "yes" - how? > > dlopen? That's be one way. Also, most systems have shared libraries > in /usr/lib and these routines are meant to be linked against and > used. For example, on darwin, there sinf is resolved from a shared > library, you declare it and call it, as

Is it possible to use dynamic library (*.so *.dll) from bytecode? If "yes" - how? -- WBR, Yaroslav Kavenchuk.

Chris Lattner wrote: >> $ lli gcd_ui.bc >> ERROR: Program used external function '__gmpz_init_set_ui' which could >> not be resolved! >> >> This application has requested the Runtime to terminate it in an >> unusual way. >> Please contact the application's support team for more information. > > Try: lli -load /path/to/foo.so gcd_ui.bc

On Jun 18, 2008, at 12:27 PM, Yaroslav Kavenchuk wrote: > Mike Stump wrote: >>> Is it possible to use dynamic library (*.so *.dll) from bytecode? >>> If "yes" - how? >> >> dlopen? That's be one way. Also, most systems have shared libraries >> in /usr/lib and these routines are meant to be linked against and >> used. For example, on

On Jun 18, 2008, at 6:48 AM, Yaroslav Kavenchuk wrote: > Is it possible to use dynamic library (*.so *.dll) from bytecode? > If "yes" - how? dlopen? That's be one way. Also, most systems have shared libraries in /usr/lib and these routines are meant to be linked against and used. For example, on darwin, there sinf is resolved from a shared library, you declare it and

On Jun 18, 2008, at 12:27 PM, Yaroslav Kavenchuk wrote: > $ llvm-gcc.exe -I/mingw/include gcd_ui.c -L/mingw/lib -lgmp -o > gcd_ui.ll -emit-llvm -S Use > $ llvm-as gcd_ui.ll -o gcd_ui.bc Use llc gcd_ui.bc and then llvm-gcc.exe gcd_ui.s -L/mingw/lib -lgmp?

mingw, llvm 2.6 (buid with llvm-gcc) Example source code: http://npcontemplation.blogspot.com/2008/06/secret-of-llvm-c-bindings.html I change LLVMCreateJITCompiler(&engine, provider, &error); to LLVMCreateJITCompiler(&engine, provider, 3, &error); $ llvm-gcc `llvm-config --cflags` -c fac.c $ g++ `llvm-config --libs --cflags --ldflags core analysis executionengine jit

you want to use the execution engine and JIT but do not put them in the llvm-config line?? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091106/d26a0a02/attachment.html>

Updated today, got Typo 2.6.0 broken with Rails 1.1 (Ruby 1.8.4) -- WEBrick does not start. Is there any workaround except "svn co" with Typo trunk? -- Yaroslav Markin yaroslav at markin dot net

Some issues about bytecode libraries, their names, and where they get installed need to be discussed. Currently the bytecode libraries are installed to two different places: $(libdir) $(bytecode_libdir) libdir is $(prefix)/lib bytecode_libdir is $(LLVMGCCDIR)/bytecode-libs The things that go into $(libdir) are built from the "runtime" directory but aren't bytecode libraries,

Hi Ryan, On Fri, 2006-12-01 at 18:06 -0600, Ryan M. Lefever wrote: > I am trying to disassemble some bytecode using llvm-dis: > llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc > > However, I am getting the following error. > > llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) The problem is most likely that sliceme2.cbc is *not* bytecode. Open the

Hi: For some reason, I changed the files /ByteCode/Writer/Writer.cpp and /ByteCode/Reader/Reader.cpp and I introduced an new version number 6. Now I replaced these two changed files with the original ones that are version 5. And I rebuild the llvm compiler. What make me mad is that the bytecode produced now is still version 6! Of course the reader cannot recognize it because the current reader

Hi, I'm changing bytecode format a little bit, i.e. for 2 operands Instructions, the original is like this: 01-00:Opcode type 07-02:Opcode 15-08: Instruction type 23-16: Operand#1 31-24: Operand#2 My change is like this: 01-00:Opcode type 07-02:Opcode 15-08: Instruction type 16: myflag1 17: myflag2 24-18: Operand#1 31-25: Operand#2 I do

On Wed, 12 Oct 2005 shding at mtu.edu wrote: > For some reason, I changed the files /ByteCode/Writer/Writer.cpp and > /ByteCode/Reader/Reader.cpp and I introduced an new version number 6. > Now I replaced these two changed files with the original ones that are > version 5. And I rebuild the llvm compiler. What make me mad is that > the bytecode produced now is still version 6! Of

Kenneth Hoste wrote: > John Criswell wrote: >> Okay. As Rob has already said, it sounds like you want to write an >> LLVM pass that adds global variables and instructions to a program. >> So, to state it explicitly, you want to: >> >> 1) Compile the program that you want to instrument to LLVM bytecode >> using llvm-gcc. >> 2) Use an LLVM pass that

On Thu, 8 Jan 2004, Grant Gould wrote: Dear Mr. Gould, > Is there any documentation of the llvm bytecode format? I looked > around the website but didn't see any; did I miss some obvious > document? At this time, we do not have any documentation on the bytcode format. I believe one LLVM user was working on such a document at one time, but if so, it is not complete. One option

I did this short experiment: ggreif at my [!297] cd /home/ggreif/llvm ggreif at my [!298] find . -name "*.cpp" | xargs grep bytecode | wc -l 143 I guess these are a quick prey for perl's in-place replace. But wait! There are more: ggreif at my [!299] find . -name "*.cpp" | xargs grep -i bytecode | wc -l 291 probably all of the rest is "Bytecode"

All, Post 1.9 we will start using bytecode version 7. Version 6 corresponds to release 1.9. There is some work that needs to be done to make this happen but I'm too tired to think through it right now. I will address this first thing in the morning. In the meantime, the CVS head version of LLVM just changed what version 6 bytecodes means. That means your old version 6 bytecode (before the

Anyone, can you say what was the reason to rename bytecode? I am still interesting in 2010/9/29 Duncan Sands <baldrick at free.fr> Hi Ariel, > As long as I know English the word "bit" is a "small pice", . Why in set of > documentation ir is "bytecode", in other set or llvm source is "bitecode"? > What is the right? Different people call the

I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compiled using the same version of llvm-gcc as llvm-dis. -- Ryan M. Lefever