search for: parrt

On Apr 22, 2008, at 5:43 PM, Gordon Henriksen wrote: > This is not possible for instructions (which must be in SSA form). You > can only use it for constants. > > http://llvm.org/docs/LangRef.html#constantexprs ah! ok, but really helpful for structs init. cool. >> I'm always using the pure text input headline generating everything >> from Java... > > Normally

...tually, is that for LLVM in particular the C+ + API offers more safety, and emitting .ll generally requires at least partially reimplementing the IR object model. I think this is a topic in the FAQ. But both are perfectly valid approaches! - Gordon On Apr 23, 2008, at 14:04, Terence Parr <parrt at cs.usfca.edu> wrote: > Gordon reminded me that most people seem to generate code using code, > whereas it has become natural for me to use templates to generate > code. Let me include an example from an article I'm working on (Java > centric). The same argument goes for LLVM...

Gordon reminded me that most people seem to generate code using code, whereas it has become natural for me to use templates to generate code. Let me include an example from an article I'm working on (Java centric). The same argument goes for LLVM IR templates versus using the C++ interface. Generating LLVM IR for me is super simple. Here are a few of my templates for generating IR

Hi, I've been spending hours looking for example language -> IR translations so I can learn more about the IR. I also looked for a simple-to-setup project that would give the samples. Finally, I downloaded list archives (are they visible to google?) and scanned. Found -emit-llvm option on llvm-gcc. This is your friend. It answers "how do I represent x in IR?". E.g.,

Howdy, I need binaries of llvm 2.2 tools like llvm-as for my students...i'm putting here if someone wants to check 'em out. First one is intel mac: http://www.antlr.org/download/llvm/ just jumped into my /usr/local and tar'd up everything that was in bin/ etc/ include/ lib/ related to llvm. --prefix on configure was / usr/local. Building fedora linux intel as we speak. Ter

Howdy, I just finished a book called Language Implementation Patterns but I ran out of room at 400 pages before I could squeeze in an LLVM example. I left a link in the book to the ANTLR wiki so I can slap something together: http://www.antlr.org/wiki/display/ANTLR3/LLVM The code is good but the description was slapped together I'm afraid (i.e., don't take it as an example of the book

On Apr 22, 2008, at 3:27 PM, Gordon Henriksen wrote: > If you'd like to propose clarified language once you've wrapped your > head around the framework, I'd be happy to incorporate it. Most > ideally, submit a patch against GarbageCollection.html in http://llvm.org/svn/llvm-project/llvm/trunk/docs/ > . Cool. Ok, I have already submitted some svn diffs to Chris to fix

Howdy do LLVM folks! I've exhausted what I can do on my own to make a GC example bind (usual googling, reading, playing, looking at source). I can't find the shadow collector lib or perhaps the -l options needed to link my sample (not even to point where I'm figuring out GC actually as I can't link). Not sure this IR is correct but here is what I've been playing

Ok, I *might* be getting this from the assembly code. The assembly code has: L_llvm_gc_root_chain$non_lazy_ptr: .indirect_symbol _llvm_gc_root_chain .long 0 and I see it being used in the function preamble. Is that a ref to an extern symbol or the def? I.e., is it referring to StackEntry *llvm_gc_root_chain; that I must have in my GC C code? (semispace.c has it) SO!

On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote: > The shadow stack walker is in the runtime directory with the semispace > heap example. The runtime directory is built to LLVM IR using llvm- > gcc. So it's skipped unless you configure llvm with llvm-gcc support. doh! That's how I missed the binary. thanks! > Since the semispace heap doesn't actually work (it's

On Apr 20, 2008, at 6:52 PM, Gordon Henriksen wrote: > On 2008-04-20, at 21:05, Terence Parr wrote: > >> On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote: >> >>> Since the semispace heap doesn't actually work (it's an example, >>> at best), I suggest you simply copy the stack visitor into your >>> project; it's only a dozen lines of

On Apr 21, 2008, at 6:23 PM, Gordon Henriksen wrote: > On Apr 21, 2008, at 20:09, Terence Parr wrote: > >> Ok, I *might* be getting this from the assembly code. ... From >> that, it will push/pop in functions? If so, that's easy enough. :) > > Yup! Sounds like you've got it. Yup, what i was missing and what somebody should add to the doc is that