similar to: [LLVMdev] Memory Alignment, Heap allocation.

On Mon, 14 Jun 2004, Tobias Nurmiranta wrote: > A small question: How do I ensure memory alignment? I want all malloced > memory, globals and functions to be 4-byte aligned. Does llvm have any > ".align" keyword? In the medium term, we plan to add alignment requirements to the alloca/malloc instructions and to globals (vars/functions) but we do not have this yet. Currently

Tobias Nurmiranta wrote: > Hi, Chris and others can give you better ideas on the ideal ways to implement what you want, but I'll give some ideas/answers for now. > > 1. > > A small question: How do I ensure memory alignment? I want all malloced > memory, globals and functions to be 4-byte aligned. Does llvm have any > ".align" keyword? No, LLVM does not

Hi, now I've had some free coding time. On Mon, 14 Jun 2004, Chris Lattner wrote: > Writing a scheme front-end for LLVM sounds like a great project: please > keep us informed how it goes, and when it gets mostly functional, let us > know so we can add a link on the web site. :) > > -Chris Just to keep you informed. My small scheme compiler[1] of 1K lines is now self

Hi, thanks for your mail! On Sat, 17 Jul 2004, Chris Lattner wrote: > > That is wonderful! Wow, you did this just ~1 month? :) Yes :), even less, but that is since I used the structure from SICP, see the URL below. > Cool, ok. Have you seen the LLVM GC support that is already available: > http://llvm.cs.uiuc.edu/docs/GarbageCollection.html > > It should be able to support

On Sat, 17 Jul 2004, Tobias Nurmiranta wrote: > > Hi, now I've had some free coding time. > > On Mon, 14 Jun 2004, Chris Lattner wrote: > > Writing a scheme front-end for LLVM sounds like a great project: please > > keep us informed how it goes, and when it gets mostly functional, let us > > know so we can add a link on the web site. :) > > > >

On Sun, 18 Jul 2004, Tobias Nurmiranta wrote: > > Cool, ok. Have you seen the LLVM GC support that is already available: > > http://llvm.cs.uiuc.edu/docs/GarbageCollection.html > > > > It should be able to support scheme well, though there may be some missing > > bits. > > Yes, I will read/use it closer and try to use it, and say if I miss > something.

I wrote As a beginner, I agree .... the for loop is much clearer to me. Wacek Kusnierczyk <Waclaw.Marcin.Kusnierczyk at idi.ntnu.no> replied > >well, that's quite likely. especially given that typical courses in >programming, afaik, include for looping but not necessarily functional >stuff -- are you an r beginner, or a programming beginner? > Both. My PhD is in

On Sat, 17 Jul 2004, Chris Lattner wrote: > > http://www.ida.liu.se/~tobnu/scheme2llvm/ > > Looks great! > > > (what's a blurb? :) > > Just a summary, so that I can add an entry to this page: > http://llvm.cs.uiuc.edu/ProjectsWithLLVM/ Maybe this for now: "This is a small self applicable scheme compiler for LLVM. The code is quite similar to the code in

Hello, What can I read to learn more about interpreters in general and the R interpreter in particular? As for my level of computer competence, I can maintain my Linux system pretty easily and I can program a bit in C and Python. TIA, Robert Burrows rbb at nebiometrics.com -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > [1] I'm kind of newbie of cvs, but I did: > "cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm diff llvm > gcpatch" That patch is well formed. You did exactly the right thing. :) > Ok, a patch[1] is attached. I didn't care to coerce the offset, since I > assume that it is an uint, but maybe I should?

On Mon, 19 Jul 2004, Tobias Nurmiranta wrote: > Regarding llvm.gcroot, do I have to allocate stack-space for all > pointers in a function? Right now I mostly use SSA-variables, and let > llvm's register allocation allocate stack-space when needed. Yes. This reflects the fact that the GC can move objects (to compact the heap) at unpredictable times. > Also, what happens when I

On Mon, 19 Jul 2004, Tobias Nurmiranta wrote: > > Not currently. In the future this will definitely be improved. In > > particular, when the code generators are enhanced to provide more accurate > > mapping information for GC pointers (e.g. which registers contain > > pointers), we can do this. This is in the long term plans, but I suspect > > that performance will

On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > This will work, but it would be better to take two pointers in instead of > a pointer and offset. This allows the front-end to emit target-generic > code instead of target-specific code (where it would have to know the > offset to the field). To be more specific, llvm_gc_read should

On Mon, 19 Jul 2004, Chris Lattner wrote: > On Mon, 19 Jul 2004, Tobias Nurmiranta wrote: > > > Regarding llvm.gcroot, do I have to allocate stack-space for all > > pointers in a function? Right now I mostly use SSA-variables, and let > > llvm's register allocation allocate stack-space when needed. > > Yes. This reflects the fact that the GC can move objects (to

Dear Users, I would like to use compositions package with ggplot/ggtern, other composition classes of compositional package can be used with ggtern by converting to data frame but I could do anything with c(ount)comp class. Ggplot/ggtern can not recognise comp and also can not be converted to data frame. Is there any other way to do this? Thank you in advance, Levent TERLEMEZ.

Upon setting up and configuring the my extension.conf, meetme.conf and following the instruction outlined at this web page: http://www.voip-info.org/wiki-Asterisk+timer+ztdummy I get the following errors when calling the meetme number. Executing Wait("SIP/216.53.118.2-f41196e0", "1") in new stack -- Executing MeetMe("SIP/216.53.118.2-f41196e0",

On Wed, 18 Aug 2004, Reid Spencer wrote: > On Wed, 2004-08-18 at 11:54, Tobias Nurmiranta wrote: > > Okay. I'm not an expert on GC but I'll take a look ... Thanks :) > > > For some strange reason I get segmentation fault in process_pointer in > > semispace.c (I've implemented a small collector, hopefully :). The fault > > occurs when I do: > > >

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > return *FieldPtr; > > } > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > cases? For the field pointer, one could use the getelementptr instruction: %pairty = { sbyte, sbyte, int* } %pairPtr = ... %fieldptr = getelementptr

Suppose I have a formula like this: f <- y ~ qss(x, lambda = lambdas[1]) + qss(z, lambdas[2]) + s I?d like a function, g(lambdas, f) that would take g(c(2,3), f) and produce the new formula: y ~ qss(x, lambda = 2) + qss(z, 3) + s For only two qss terms I have been using g <- function(lambdas, f){ F <- deparse(f) F <- gsub("lambdas\\[1\\]",lambdas[1],F) F

I'm implementing a lazy functional language and I need to allocate nodes on the heap. From what I've read LLVM supports only the 'alloca' instruction which allows to allocate memory on the stack. Is this true and and if so, what is the preferred way to solve my problem? -- Piotr Kaleta -------------- next part -------------- An HTML attachment was scrubbed... URL: