search for: tp33486161p33486962

...st re-allocate it as a { i32, [5 x i32] } when I learn about the length? That doesn't sound like the nicest option. I'm not aware of a way of only allocating a part of a literal struct, is that possible? Cheers, Fraser -- View this message in context: http://old.nabble.com/LLI-Segfaulting-tp33486161p33486962.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

...sn't sound like the nicest option. I'm >> not >> aware of a way of only allocating a part of a literal struct, is that >> possible? >> >> Cheers, >> Fraser >> -- >> View this message in context: >> http://old.nabble.com/LLI-Segfaulting-tp33486161p33486962.html >> Sent from the LLVM - Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvm...

...} when > I learn about the length? That doesn't sound like the nicest option. I'm not > aware of a way of only allocating a part of a literal struct, is that > possible? > > Cheers, > Fraser > -- > View this message in context: http://old.nabble.com/LLI-Segfaulting-tp33486161p33486962.html > Sent from the LLVM - Dev mailing list archive at Nabble.com. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...9;m > >> not > >> aware of a way of only allocating a part of a literal struct, is that > >> possible? > >> > >> Cheers, > >> Fraser > >> -- > >> View this message in context: > >> http://old.nabble.com/LLI-Segfaulting-tp33486161p33486962.html > >> Sent from the LLVM - Dev mailing list archive at Nabble.com. > >> > >> _______________________________________________ > >> LLVM Developers mailing list > >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > >> http://lists.cs.u...

...gt;> aware of a way of only allocating a part of a literal struct, is that >> >> possible? >> >> >> >> Cheers, >> >> Fraser >> >> -- >> >> View this message in context: >> >> http://old.nabble.com/LLI-Segfaulting-tp33486161p33486962.html >> >> Sent from the LLVM - Dev mailing list archive at Nabble.com. >> >> >> >> _______________________________________________ >> >> LLVM Developers mailing list >> >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> &g...

Hi Fraser, it looks to me like you are smashing the stack. > define void @main() nounwind { > allocas: > %0 = alloca { i32, [0 x i32] }, align 8 ^ this allocates 4 bytes on the stack. > %2 = getelementptr inbounds { i32, [0 x i32] }* %0, i64 0, i32 1 ^ this gets a pointer to the byte after the 4 allocated bytes. > %3 = bitcast [0 x i32]* %2 to i8* > call void

Hi, I've been stuck with this problem for a while now, and my supervisor's starting to think it's a bug in lli, but I thought I'd ask here before going down that route. I have this code, which stores an array in my 'MainClass', and prints out an element of it. Note that the print statement is irrelevant here, it segfaults regardless, and this code has been run with -O2