similar to: [LLVMdev] how to read the llvm source-file?

Constant *strcon==ConstantArray::get("Value : %d\n"); Sorry Typo. On Tue, 21 Dec 2004, Misha Brukman wrote: > On Tue, Dec 21, 2004 at 03:45:33PM -0700, Sriraman Tallam wrote: > > I have this call instruction to printf inserted which is causing > > an assertion failure. Any pointers to where I am wrong : > > > > Function

Actually, Misha, that won't work. The -C option is used directly in docs/Makefile. So the change will have to go into docs/Makefile. Either that or upgrade install to version 5. Reid. On Thu, 2005-02-17 at 11:33, Misha Brukman wrote: > On Thu, Feb 17, 2005 at 01:21:20PM -0600, Feng Chen wrote: > > llvm[1]: Installing HTML documentation > >

Hello list, I've been having a tough time adding windows resource support to my ogg vorbise decoder, although I think I am close. Basically when I call ov_open_callbacks(), it doesn't ever return and repeatedly calls my seek_func. I'm hoping it is something obvious, but I can't see why my seek_func is being called endlessly. If the file is seekable, I should return 0, right? If

On Wed, Jun 23, 2004 at 03:50:09PM -0500, Patrick Meredith wrote: > MetaSplit is an anlysis I just finished writing. It doesn't alter > anything, all it does is build a set of "program instructions". For > some reason even though if I run it with any other combination of > passes I've found, anytime I run it with mem2reg I get a seg fault in > dyn_cast!

Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" but there was no output. Maybe this is the probelm, I do have CXX = g++ -mcpu=v9 CC := gcc -mcpu=v9 in the Makefile.config. Do I need to add -m64 as well? Thanks. Shukang On Thu, 7 Oct 2004, Misha Brukman wrote: > Is your compiler configured to define __sparcv9 when it compiles? > The following should tell

On Wed, 11 Jan 2006, Reid Spencer wrote: > llvm-as file.bc | opt -mem2reg | llvm-dis > file.ll llvm-as < file.bc | opt -mem2reg | llvm-dis > file.ll Note the extra "<". -Chris > On Wed, 2006-01-04 at 09:12 +0800, lizhuo wrote: >> meone tell me how to convert LLVM bytecode into minimal SSA form ? >> or just depend on GCC frontend ? > -Chris --

On Tue, Dec 21, 2004 at 03:53:47PM -0700, Sriraman Tallam wrote: > Constant *strcon==ConstantArray::get("Value : %d\n"); OK, then what's the assertion? You can also see the resulting module by using -disable-verify: $ opt -yourpass -disable-verify < file.bc | llvm-dis You may see what the problem is by looking at the LLVM assembly. -- Misha Brukman ::

On Fri, 20 Aug 2004 08:52:28 -0700 Reid Spencer <reid at x10sys.com> wrote: > Hi Jeff, > > On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote: > > OK. I've built the front end without any heartaches, but I did > > encountered the following glitches: > > > > The documentation of --with-llvmgccdir is a bit ambiguous. I had to > > try several paths

I'm having an issue sourcing an R file from my workbench using StatET in the Eclipse IDE. All I'm trying to do is get comfortable with 'source' and run "source(C:/Program Files (x86)/Eclipse/eclipse/ProjectName/SourceFile.R)". When I try to call the path for the file i get the error: "unexpected '/' in "source(C:/". I've looked around but

On Thu, Feb 17, 2005 at 11:39:27AM -0800, Reid Spencer wrote: > Actually, Misha, that won't work. Sorry, Reid, but I think it will, for the following reason: I don't really know what the -c (lowercase) option does, but install says it's ignored anyway, so that's irrelevant for GNU install. We're talking about the -C option (uppercase). > The -C option is used directly

On Wed, 23 Jun 2004, Patrick Meredith wrote: > What's different about code that's been mem2reg'd from straight front end > code, or anything that mem2reg hasn't been run on? PHINODES! Yup, front-ends generally don't produce SSA form. :) > It appears to be crashing when I try to cast a Value* that's really a > BB* (from the PHInode operands) to a User*,

On Fri, Sep 24, 2004 at 09:38:44AM -0700, Jeff Cohen wrote: > Here's the patch to Signals.cpp. assuming that stdio.h is acceptable > (can't imagine it won't work). We prefer #include <cstdio>, since this is C++ after all. :) -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

Reid Spencer wrote: >Yes, that's right! > >In fact, shortly the process of doing that will get easier with the >llvmc (compiler driver) tool that I'm working on. You write your >compiler to generate either bytecode or LLVM assembly and a > > Does that mean the front end must decide between emiting bytecode for interpretting/JITing and LLVM assembly for native

Here's the patch to Signals.cpp. assuming that stdio.h is acceptable (can't imagine it won't work). On Fri, 24 Sep 2004 09:29:05 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > Uh... this may be a silly question, but why can't you include <stdio.h>? > It'd be much better than <iostream>. > > Anyway, I think I'll try this weekend to come

On Fri, Sep 03, 2004 at 03:01:01PM -0500, Anshu Dasgupta wrote: > ><snip> > >for (BasicBlock::iterator I = Dest->begin(); PHINode *PN = > >dyn_cast<PHINode>(I); ++I) > > visitPHINode(*PN); > ><snip> > > > >build_vc71\lib\Transforms\Scalar\SCCP.cpp(202) : error C2275: > >'llvm::PHINode' : illegal use of this type as

I'm CC'ing the llvm-dev list because other people are more knowledgeable about the bytecode format/encoding than I am. Please follow-up the replies to the list. On Wed, Oct 20, 2004 at 11:27:53AM -0700, Yiping Fan wrote: > We also want to extend the llvm instructions/intrinsic > functions/types/passes to support our high-level synthesis for > hardware. First of all, we want to

On Wed, Aug 04, 2004 at 12:16:12PM -0700, Reid Spencer wrote: > So I propose: > [snip] > -O3 = aggressive optimization, regardless of computation time with the > effect of producing the fastest executable I would suggest splitting -O3 into 2 or more levels of optimization, because as written, -O3 sounds pretty scary: "regardless of computation time", and given some

Hi all, I get this warning during compilation: make[3]: Entering directory `/home/wendling/llvm/llvm/lib/ExecutionEngine/JIT' Compiling Emitter.cpp Emitter.cpp:44:1: warning: "_POSIX_MAPPED_FILES" redefined In file included from /usr/include/unistd.h:171, from /usr/include/c++/3.3.1/i586-mandrake-linux-gnu/bits/gthr-default.h:38, from

On Sat, Aug 21, 2004 at 04:15:49PM -0700, Jeff Cohen wrote: > I don't know if it's under cvs. It's the "getting started" page > (http://llvm.cs.uiuc.edu/docs/GettingStarted.html) in section "Getting > Started Quickly (A Summary)". But careful reading of the remainder of > the page does give the correct path. http://llvm.cs.uiuc.edu/docs/* is a copy of

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. In the meantime, people are welcome to what I have