similar to: [LLVMdev] bytecode documentation?

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

Well, I compiled release but it gave error while making png library. The inclusion of zlib.h in the file png.h cannot locate file zlib.h. If you change the inclusion to include "../zlib/zlib.h" instead of just "zlib.h" in png.h then compilation succeeds. regards,

Well, I compiled release but it gave error while making png library. The inclusion of zlib.h in the file png.h cannot locate file zlib.h. If you change the inclusion to include "../zlib/zlib.h" instead of just "zlib.h" in png.h then compilation succeeds. regards,

Hi, I want to check some properties of linux kernel with llvm, but I don't know how to compile a linux kernel to an llvm's .bc file. I have let llvm's gcc front-end ignore inline assembly by modifying cfrontend/src/gcc/llvm-expand.c, and replace CC/as/ar in the Makefile of the kernel with llvm-gcc/llvm-as/llvm-ar. However, the linux's "make" reports errors:

Might anyone have a FreeBSD binary or suggested modifications to the source to compile one? Thanks, Sean

> For example: > $ llvmgcc ackerman.c -o ackerman -Wl,-native-cbe BTW, Chris, what should be then an analogy of "gcc -O3 -S foo.c" in LLVM framework? The invocation of $ llvmgcc -S ackerman.c -o ackerman -Wl,-native-cbe does not produce native assebler output as one might expect. -- Valery

On Wed, 2004-08-04 at 12:21, John Criswell wrote: > In regards to Misha's comments about the automatic execution of bytecode > files, there are several ways to do it: > > 1) Have bytecode files start with #!<JIT/llee/whatever> (portable) > 2) Encapsulate with ELF > 3) Register the type with the kernel (Linux only) > > I don't really care for the llee

This is a interesting thread. I think this would also help with compiling scripting languages such as JavaScript/Python etc. We could keep the high level meta data and runtime binding info as language specific bytecode in the file and just have the parts that are easy to represent as compileable in the main object sections. There is no intrinsic reason for all the runtime type information to get

I don't know the current status of the LLVA project, so I will let the current developers chime in. Please send all LLVM and LLVA questions to llvmdev at cs.uiuc.edu . ----- Forwarded message from N O S P A M <ti_dak at yahoo.com> ----- Date: Tue, 17 Jan 2006 09:47:32 -0800 (PST) From: N O S P A M <ti_dak at yahoo.com> Subject: LLVA, TAO Intent, Morphun, DualCor Hello I want to

Dear All, Do people think that they are ready to create the LLVM 1.6 release branch? I believe all the development is pretty much done. Is all the documentation in the LLVM source tree updated and ready? I'm not able to make a full doc review like I've been able to do in previous releases, so I need volunteers to work on the docs if they're not done yet. -- John T. -- John

> I can run that pass through opt on the bytecode emitted by gcc frontend > through opt tool. However, I want that Pass1 to be the part of the > actual GCC compiler. I want to know how I can position Pass1 among > other passes /optimizations/ code generations. I had a similar question and Chris recommended that I edit the addPassesToEmitAssembly method. Quoting him: "

Is the source code for llva available esp the linux kernel port. Is there a project page for llva ? Mike On 2/3/06, John Criswell <criswell at cs.uiuc.edu> wrote: > Misha Brukman wrote: > > I don't know the current status of the LLVA project, so I will let the > > current developers chime in. Please send all LLVM and LLVA questions to > > llvmdev at cs.uiuc.edu .

Hi Reid, Reid Spencer schrieb: > I have some thoughts on this too .. > Great! > On Fri, 2006-02-24 at 19:56 +0100, Jakob Praher wrote: > >>I get you 100 % here. But as you say later in the mail, many information >>is done by some runtime std::map<Value*,foo> stuff. Which is really >>handy at runtime, but I *had* serialization in mind when I was thinking

Dear All, Here is a more complete list of regressions for the platforms listed below. Some of the regressions from the previous list I emailed a few days ago have been fixed or were false positives. Thanks to all who've helped fix things. We would like to try to get as many of these fixed as possible before I create the release branch (still scheduled for tomorrow, Friday). I'll

Suppose, I have a Pass1 implemented as a subclass of Pass, with source code in the directory of llvm source base( transform/analyze ) I can run that pass through opt on the bytecode emitted by gcc frontend through opt tool. However, I want that Pass1 to be the part of the actual GCC compiler. I want to know how I can position Pass1 among other passes /optimizations/ code generations. e.g if

On Thu, 12 May 2005, John Criswell wrote: > Here is a more complete list of regressions for the platforms listed below. > Some of the regressions from the previous list I emailed a few days ago have > been fixed or were false positives. Thanks to all who've helped fix things. > > We would like to try to get as many of these fixed as possible before I > create the release

Hi all LLVMor, I just tried to compile a simple code and analyze the number of the basic blocks. But after compile, what I got, the bytecode is seems to be optimized bytecode. So the information of basic blocks is not what I expected. I want ot use the code as example to see how some of code optimization methods work. However, after compiling file using llvm test.c -o test, bytecode file

ymxia at nudt.edu.cn wrote: > Hi, > > I want to check some properties of linux kernel with llvm, but I don't know how to compile a > > linux kernel to an llvm's .bc file. I have let llvm's gcc front-end ignore inline assembly by > > modifying cfrontend/src/gcc/llvm-expand.c, and replace CC/as/ar in the Makefile of the kernel > > with

Hi, I want to find simple loops in LLVM bytecode, and extract the basic information of the loop. For example: for (i=0; i<1000; i++) sum += i; I want to extract the bound [0, 1000), the loop variable "i" and the loop body (sum += i). What should I do? I read the LLVM API document, and find some useful classes like "Loop", "LoopInfo". But I do

I am trying to use LLVM as a source to source C compiler. I use llvm-gcc to convert file.c->file.bc. Then I use opt to run my own compiler passes to convert file.bc->file.opt.bc. Then I use llc to convert file.opt.bc->file.opt.c. Now, I want to use normal gcc to compile file.opt.c into an executable. However, I'm getting the following errors: test.opt.c:89: warning: