search for: nurmiranta

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: > &...

Seems like Root in process_root sometimes is a null pointer. Wonder if it is my fault? :) *debugging* , Tobias On Wed, 18 Aug 2004, Tobias Nurmiranta wrote: > > 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...

On Thu, 22 Jul 2004, Chris Lattner wrote: > On Thu, 22 Jul 2004, Tobias Nurmiranta wrote: > > Hmm, it felt nicer to mark raw LLVM pointers as roots and then transform > > them, since I then didn't have to see the overhead in my frontend :). > > I'm not sure what overhead you mean. I think I should have emphasized "felt", since it only would ma...

Thanks for the fast reply. I'll do as you suggested, and create my own identity instructions with "add" for int's and "getelementptr" for pointers. , Tobias On Thu, 17 Jun 2004, Misha Brukman wrote: > On Thu, Jun 17, 2004 at 05:09:30PM +0200, Tobias Nurmiranta wrote: > > A small thing I miss in the intermediate representation is a simple > > assignment instruction, like: > > > > %x = uint 3 > > or: > > %x = uint %y > > > > It would simplify the implementation of frontends, I think. > > Neither of...

...t; should I use to optimize away these alloca's? In most cases it is more convenient for me to use SSA-registers, but for example if-statements and some others, it is nicer to use alloca. Thanks for the advice. , Tobias On Thu, 17 Jun 2004, Chris Lattner wrote: > On Thu, 17 Jun 2004, Tobias Nurmiranta wrote: > > > > Thanks for the fast reply. I'll do as you suggested, and create my own > > identity instructions with "add" for int's and "getelementptr" for > > pointers. > > Another thing to point out is that this might only be happening be...

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 offse...

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...

...ad. Thank you. , Tobias On Sat, 12 Jun 2004, Reid Spencer wrote: > Hi Tobias, > > I tried your test program on the latest CVS code. Everything worked > fine. > > Can you tell me which version of LLVM you're using? > > Reid. > > On Sat, 2004-06-12 at 08:26, Tobias Nurmiranta wrote: > > Hi, > > > > I'm trying to compile and run the following code-snippet: > > > > implementation > > > > uint %fie(uint* %x) { > > %e = getelementptr uint* %x, int 1 > > ; %f = load uint* %e > > ret uint 3 > >...

On Thu, 17 Jun 2004, Tobias Nurmiranta wrote: > > Thanks for the fast reply. I'll do as you suggested, and create my own > identity instructions with "add" for int's and "getelementptr" for > pointers. Another thing to point out is that this might only be happening because your front-end is atte...

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 h...

Hi, I'm thinking out loud, please give me some feedback. Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are implemented as: llvm.gcread(sbyte** object, uint offset) llvm.gcwrite(sbyte* data, sbyte** object, uint offset) Where you also have the offset into the object. In this way the GC would know where the header of the object we are reading/writing to is. Also

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...

On Wed, 2004-08-18 at 11:54, Tobias Nurmiranta wrote: > Hi, > > This is regarding the backend for garbage collection. My problem might be > related to some strange memory fault created by my frontend, but I'll try > here to get some feedback. Okay. I'm not an expert on GC but I'll take a look ... > For some stra...

Hi Tobias, I tried your test program on the latest CVS code. Everything worked fine. Can you tell me which version of LLVM you're using? Reid. On Sat, 2004-06-12 at 08:26, Tobias Nurmiranta wrote: > Hi, > > I'm trying to compile and run the following code-snippet: > > implementation > > uint %fie(uint* %x) { > %e = getelementptr uint* %x, int 1 > ; %f = load uint* %e > ret uint 3 > } > > int %main(int %argc, sbyte** %argv) { &...

On Thu, Jun 17, 2004 at 05:09:30PM +0200, Tobias Nurmiranta wrote: > A small thing I miss in the intermediate representation is a simple > assignment instruction, like: > > %x = uint 3 > or: > %x = uint %y > > It would simplify the implementation of frontends, I think. Neither of these is necessary, and adding new instructions...

Hi. A small thing I miss in the intermediate representation is a simple assignment instruction, like: %x = uint 3 or: %x = uint %y It would simplify the implementation of frontends, I think. , Tobias

Hi, I'm trying to compile and run the following code-snippet: implementation uint %fie(uint* %x) { %e = getelementptr uint* %x, int 1 ; %f = load uint* %e ret uint 3 } int %main(int %argc, sbyte** %argv) { %z = malloc uint, uint 10 %g = call uint %fie(uint* %z) ret int 0 } But the getelementptr instruction gives a segmentation fault. Have I misunderstood its use? I

Hi, This is regarding the backend for garbage collection. My problem might be related to some strange memory fault created by my frontend, but I'll try here to get some feedback. 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: printf("process_root[0x%p] = 0x%p\n",

On Thu, 22 Jul 2004, Tobias Nurmiranta wrote: > > Unfortunately this won't really work. It might be reasonable to include > > something like this in the front-end that you're working on, but including > > this at the LLVM level is a bad idea. The basic idea of the alloca model > > is that it directly ex...

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 mo...