similar to: [LLVMdev] Bytecode Format Manual

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

Sean Peisert wrote: > John, > > I may be missing something here, but if I the compilation docs, I need > to build LLVM first and the C frontend second. But doing this, I > get: > > **llvm-gcc/llvm-g++ was not found, > > (obviously -- it wasn't installed, right?) You do need to build LLVM first before building llvm-gcc. This may seem a bit weird, but

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

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

Valery A.Khamenya wrote: >>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.

Reid Spencer wrote: > 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)

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

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 .

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 . My apologies for the late reply. > > ----- 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

Dear Boris, I managed to see your question and rescue it from the llvm-announce mailing list filter. I'm forwarding your question to the llvmdev at cs.uiuc.edu mailing list; that list is used for questions and answers about LLVM. For future reference, the llvm-announce list is used to send announcements regarding LLVM releases. The llvmdev list is for general discussion. Now, on to

Dear All, First, we're pushing back the creation of the release branch until tonight. This means two things: 1. If you want something to go into LLVM 1.5, you have until I create the release branch to get it in. I am tentatively scheduling this for 5:00 pm today (CST). 2. If you don't want something to go into LLVM 1.5, please refrain from adding it until I create the release

Long Fei wrote: > > I am investigating some inlining issue, so I did > > llvm-gcc aaa.c bbb.c ... nnn.c -o output > opt -inline -inline-threshold=xxx < output.bc | llc -march=c > > output_inline.c I am unsure of whether the LLVM GCC frontend does any inlining. However, I do know that your methods above run the LLVM inlining pass, albeit indirectly. If you use

Reid Spencer wrote: > On Wed, 2004-08-04 at 08:24, John Criswell wrote: > > >>o Configuration Files >> >>If it isn't too much trouble, I think we should go with XML for the >>following reasons: >> >>1) We wouldn't need to implement a parsing library. There are several >>XML parsing libraries available, and I'm guessing that

Dear LLVM Developers, The LLVM website, CVS repository, and SAFECode website should now be back online. Should you encounter any problems with the LLVM services, please send email to llvmdev at cs.uiuc.edu so that we may fix it. Regards, John T. Criswell ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu

I have a compiler transform that I have been working on that produces bytecode that passes the verifier. However, when I try to read that bytecode back in, I get the assertion failure below. llvm::BytecodeReader::ParseConstantPoolValue(unsigned int): Assertion `(!isa<Constant>(Result) || !cast<Constant>(Result)->isNullValue()) || !hasImplicitNull(TypeID) &&

Ryan M. Lefever wrote: > 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

Finn S Andersen wrote: > Chris Lattner wrote: > >> I can't reproduce this failure with mainline CVS using either lli or llc: >> >> $ lli -regalloc=linearscan a.out.bc >> $ echo $status >> 0 >> >> Are you sure that the CVS version is in your path? >> >> > After configure and make I run make install, which moves the executables

On Mon, 22 Mar 2004, Umar Janjua wrote: > 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. I haven't seen a reply to this on LLVM

Chris Lattner wrote: > 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

Ryan, This looks like a bug. Could you file it, please? Reid. On Thu, 2007-02-22 at 19:47 -0600, Ryan M. Lefever wrote: > I have a compiler transform that I have been working on that produces > bytecode that passes the verifier. However, when I try to read that > bytecode back in, I get the assertion failure below. > > llvm::BytecodeReader::ParseConstantPoolValue(unsigned