similar to: [LLVMdev] bytecode version

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

Which bytecode files? Perhaps the ones in the runtime library? If these were built with Bytecode V6, then the reader (V5) will not read them. Chris Lattner wrote: > 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

Thank you. I'm only consider about how the compiler comiles c program to LLVM IR. I know there should be a scanner, parser, and IR generator. But where is the main entrance and how about the flow of the process, especially about the IR generator? > shding at mtu.edu wrote: >> Hi, >> Where can I find the main function of llvm compiler in the source >> file? >>

Hi, Where can I find the main function of llvm compiler in the source file? Thanks! -- Shuhan

shding at mtu.edu wrote: > Hi, > Where can I find the main function of llvm compiler in the source file? > Thanks! Well, there's a loaded question. :) It depends on "which" compiler you mean. If you're talking about the llvm-gcc and llvm-g++ compilers (C/C++ to LLVM) then they are in the downloadable tarballs available here: http://llvm.cs.uiuc.edu/releases/. You

Hi: When I tried to use llc -march=sparcv9 to compile some llvm .bc to SparcV9, I got such error: llc: /llvm/lib/Target/SparcV9/SparcV9RegInfo.h:62: virtual void llvm::TargetRegClassInfo::markColorsUsed(unsigned int, int, int, std::vector<bool, std::allocator<bool> >&) const: Assertion `UserRegType == RegTypeWanted && "Default method is probably incorrect for

Hi: I have extended the IR for adding flag. But I just want this flag to pass through the backend machine code. I know there're several passes like register relocation, schedualing, etc. But I think I just miss the part which is used to "parser" the LLVM IR to machine code instructions. Would you give me some help? Thank you ! > On Sun, 10 Jul 2005 shding at mtu.edu wrote:

Hi, I want to annotate values in llvm, like making a flag for the operands and result of an instruction for future use. I wonder if there's any interface to do such a thing? Thanks! -- Shuhan

Hi: I want to pass some message of instructions from LLVM Internal representation to backend code. For example, I make a flag for some certain operands of certain instructions. How can it be passed to the backend instructions? Which programs I should look into? Would someone give me some idea? Thank you ! -- Shuhan

Hi, I currently write a tool to parse the LLVM bytecode file (.bc file). So I have some very basic questions: - First, about the Abbreviation ID ( "0"=END_BLOCK, "1"=ENTER_SUBBLOCK...): how to read these ID from the file stream ? I mean, I don't know, how many bit length they are. It doesn't exist on the document. - Second, how is the order to read the bytecode ? For

Hi, In the directory of lib/CodeGen/SelectionDAG, I cann't find SelectionDAGISel.cpp. I only have DAGBuilder.cpp and SelectionDAG.cpp. I don't know why. My edtion is 1.4. Is it because of the edtion difference? Thanks! > On Mon, 11 Jul 2005 shding at mtu.edu wrote: >> I have extended the IR for adding flag. But I just want this flag to >> pass through the backend

As the title. Thank! -- Shuhan

Robert Mykland wrote: > Dear Chris and Reid: Hi Robert. > > Some other random ideas I've had as I've been sifting through the new > bytecode format. Please let me know what you think. > > 1) ANSI C allows for char to default to unsigned char. This is I guess > not how it normally is in GCC. If char defaulted to unsigned char > several things would be

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

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

> The point here is that XPL needs to keep track of what a given variable > represents at the source level. If the compiler sees a map that is > initially small it might represent it in LLVM assembly as a vector of > pairs. Later on, it gets optimized into being a hash table. In order to > do that and keep track of things, I need to know that the vector of > pairs is

On Sun, 2003-11-16 at 13:01, Vipin Gokhale wrote: > While on the subject of annotating bytecode with analysis info, could I > entice someone to also think about carrying other types of source-level > annotations through into bytecode ? This is particularly useful for > situations where one wants to use LLVM infrastructure for its > whole-program optimization capabilities,

Hi, I have some problems when I use this command: gcc hello.s -o hello.native(for example) to assembly the native language to a program. I always got a error message like this : "gccas: hello.s:3: parse error, unexpected $undefined. hello.s:3: while reading token: '.' " I don't know what's wrong here. By the way, when I learned llvm at the first time, I followed

I'm a new guy for llvm. I'm doing a project in which some instructions should be moved from one block into another. Those instructions may be data-dependent. When I tried to delete them one by one, it cause the error message like, " use stuck around after a def is destroyed" even if I deleted the use befor the def. When I tried to add them to another block, errors occurred like