similar to: [LLVMdev] making 2.2 binaries available

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

Hi Terence, The reason I remarked, actually, 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

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

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

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!

I'm getting a core dump with the following script: require [ "fileinto", "regex", "variables" ]; if address :domain :regex ["Reply-To", "Sender", "To", "Cc"] "antlr.org|mailman.unixodbc.org|research.att.com|wireshark.org" { if address :regex ["Reply-To", "Sender", "To",

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

On Apr 25, 2008, at 14:32, Terence Parr wrote: > Howdy. I submitted a number of documentation patches to Chris, but > he wanted your input on this one: > >>> Also, is this correct: >>> >>> %class.Array = type { %class.Object, i32, [0 x %class.Object*] } >>> ? Wondering if it should be >>> %class.Array = type { %class.Object*, i32, [0 x

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

On Apr 22, 2008, at 20:19, Terence Parr wrote: > On Apr 22, 2008, at 3:27 PM, Gordon Henriksen wrote: > >>> 1. How do I know the offset (due to alignment/padding by LLVM) of >>> a pointer within an object using {...} struct type? GEP >>> instruction gets an address, of course, but how does my C >>> collector compute these. Do I need to make a

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. > What I was/am missing is the explicit link between types and > variables in a GC.c file and the generated machine code. If I can > get that last

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

Hi again Terence, On Apr 22, 2008, at 15:20, Terence Parr wrote: > Sorry for the long questions...gotta figure this out. Not a problem! > 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

The file also has a bunch of email headers stuck in the middle of it: ..... (QUALITY-OF-LIFE SCALE:1-5 4) (ACADEMIC-EMPHASIS HEALTH-SCIENCE) ) ------- ------- >From LEBOWITZ at cs.columbia.edu Mon Feb 22 20:53:02 1988 Received: from zodiac by meridian (5.52/4.7) Received: from Jessica.Stanford.EDU by ads.com (5.58/1.9) id AA04539; Mon, 22 Feb 88 20:59:59 PST Received: from

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

I'm trying to make a regex to match common mailing list addresses and file messages to corresponding folders. I'm using sieve-test to try and understand what is happening. The sieve script is: require [ "fileinto", "regex", "variables" ]; if header :regex ["Sender"] ["(.*>[ \\t]*,?[ \\t]*)?([^-@]*)-([^-@]*)(-bounces)?@antlr.org"] {

When you create a parser via ANTLR you specify the output language of the resulting recursive descent parser, at the moment there exists no C++ output template to my knowledge, thus you would have to generate the parser as C code for which a template exists. The runtime support should be there, at least partially but it won't use things like exceptions, nor will it have a very modular design

Hi, thank you for your response. Óscar Fuentes schrieb: > It would be useful to see the first error messages and the compile > command (do make VERBOSE=1 in case it is hidden the first few errors are: f:/dev/projects/llvm-2.5/include/llvm/Support/Annotation.h:42: error: expected unqualified-id before numeric constant f:/dev/projects/llvm-2.5/include/llvm/Support/Annotation.h: In

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

Hi, I've not got any experience using ANTLR to parse C++, however, you will find that there only exists a C code generator for ANTLR and NOT a C++ one. Over the years numerous people have requested a C++ code generation template but alas there is still only a C one. Just a heads up. Granville 2009/7/11 Vikram S. Adve <vadve at cs.uiuc.edu> > We are looking for an open source C++