search for: tp33486161p33489084

Displaying 3 results from an estimated 3 matches for "tp33486161p33489084".

2012 Mar 12
1
[LLVMdev] LLI Segfaulting
...gt;> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > -- View this message in context: http://old.nabble.com/LLI-Segfaulting-tp33486161p33489084.html Sent from the LLVM - Dev mailing list archive at Nabble.com.
2012 Mar 12
0
[LLVMdev] LLI Segfaulting
Yes, that is what I mean. :-) On Mar 12, 2012 11:02 AM, "Fraser Cormack" <frasercrmck at gmail.com> wrote: > > Hi Gavin, > > Do you mean something along the lines of having my array struct as { i32, > i32* } and then indexing it with a gep and allocating the appropriate > memory > when I learn of it? > > Thanks, > Fraser > > > Gavin
2012 Mar 12
2
[LLVMdev] LLI Segfaulting
Hi Gavin, Do you mean something along the lines of having my array struct as { i32, i32* } and then indexing it with a gep and allocating the appropriate memory when I learn of it? Thanks, Fraser Gavin Harrison-2 wrote: > > Hi Fraser, > > Is there anything preventing you from using a pointer for the second part > of the structure and allocating memory for it later? > >