search for: bytecod

Hi, I am back into working on LLVM now and am having problems with Cygwin builds. Problems with both the 1.9 Release and the CVS on Cygwin... LLVM CVS Release build :- /usr/src/llvm/configure --prefix=/usr/llvm make tools-only ENABLE_OPTIMIZED=1 make[3]: Entering directory `/usr/src/lib/Bytecode/Writer' llvm[3]: Compiling SlotCalculator.cpp for Release build llvm[3]: Compiling Writer.cpp for Release build /usr/src/llvm/lib/Bytecode/Writer/Writer.cpp: In member function `void llvm::BytecodeWriter::outputConstant(const llvm::Constant*)': /usr/src/llvm/lib/Bytecode/Writer/Writer.cpp:...

This is needed for my native linker patch that is coming soon. As discussed on IRC: Index: lib/Bytecode/Archive/ArchiveReader.cpp =================================================================== RCS file: /var/cvs/llvm/llvm/lib/Bytecode/Archive/ArchiveReader.cpp,v retrieving revision 1.38 diff -u -r1.38 ArchiveReader.cpp --- lib/Bytecode/Archive/ArchiveReader.cpp 29 Dec 2004 01:20:24 -0000...

Here is the bulk of the sanitizing. My residual doubts center around the question whether we still do/want to support (un)compressed *byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached patch is for review about the IMO undisputed changes. What is still missing: - removing any genuine bytecode stuff (magic/filetype dete...

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 ver...

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...

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 file and see....

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...

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 fr...

...e various pieces of code under llvm/lib/Transforms/Instrumentation, e.g. BlockProfiling.cpp and TraceBasicBlocks.cpp. They do essentially the same thing as you are trying to do. > 1) I implement call function in another c/cpp file and > can I insert the external call function to existed > bytecode ? if it is valid. Can you give me a simple > example to show how to do it or just give me a url > which can show how to do it? Yes; in the case of BlockProfiling, it calls into the library defined in llvm/runtime/libprofile, which is linked against the resulting LLVM binary. > 2) If I&...

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 me...

Hi list, 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 same thing such differently. -- best regards Ariel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201...

Hi llvmer, I am trying to learn how to use llvm. My question is described as the following, there has already a testcase code, and I get bytecode by using llvmgcc. What I want to do is to insert a call funcation into each basic block, which is for statistic some information. 1) I implement call function in another c/cpp file and can I insert the external call function to existed bytecode ? if it is valid. Can you give me a simple example t...

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!...

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 you write to instrument the program. > 3) Use LLVM's llc program to generate C or assembly code of your > instrumented program. > 4) Compile the C/asm code to native code with gcc and link it with any > native code libraries tha...

...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 you write to instrument the program. >> 3) Use LLVM's llc program to generate C or assembly code of your >> instrumented program. >> 4) Compile the C/asm code to native code with gcc and link it with >> any n...

I'm the guy who is working on the LLVM bytecode documentation. The document I have at present just supports the bytecodes my code generator processes, though, which is far from all of them. As I get farther along with my code generator I expect I'll get to the point where everything kind of fits together for me and I can finish it up. I...

...on with SDIV, UDIV, and FDIV. These instruction changes are increments towards getting rid of signed types completely in LLVM. To reduce confusion, here's some things you need to know if you're planning to use the CVS HEAD version before the 1.9 release: 1. Release 1.9 will correspond to bytecode version 6. 2. Release 1.8 corresponds to bytecode version 5. 3. All versions of llvm-gcc/llvm prior to 11:00pm 2006-10-25 PDT will generate version 5 bytecode files. After that it llvm generates version 6. 4. Version 5 (and earlier) bytecode files will always auto-upgrade to version 6. 5. The...

..."",InsertPos); BB->getInstList().push_back(InstrCall); //BB->getInstList().insert(InsertPos,InstrCall); } > Hi llvmer, > > I am trying to learn how to use llvm. My question is > described as the following, > there has already a testcase code, and I get bytecode > by using llvmgcc. What I want to do is to insert a > call funcation into each basic block, which is for > statistic some information. > 1) I implement call function in another c/cpp file and > can I insert the external call function to existed > bytecode ? if it is valid. Can...

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? Thanks a bunch. --Grant

Here's the other of my proposals for this year's Google Summer of Code. (The first is on cfe-dev.) It was suggested to me by Dan Kegel (from the Wine project, they really want this). Title: Microsoft Direct3D shader bytecode backend Abstract: There is a distinct lack of open-source frameworks for compiling HLSL, the shader language used by Direct3D, into bytecode that D3D can understand. Currently, the only such framework is Ryan Gordon's MojoShader, whose HLSL compiler component is still under heavy development...