search for: magnifeast

Hello, Scott > I've just started using LLVM for a project I'm working on, and the > docs seem to encourage the use of alloca, with the expectation that > various optimization passes will optimize away unnecessary stack > pressure.  However, I can't seem to figure out how LLVM can properly > re-use stack space, since it doesn't know the extend of a stack >

...doesn't know the extend of a stack >> variable. > This is http://llvm.org/bugs/show_bug.cgi?id=3361 > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University > -- --------------------- Scott Shumaker CTO, magnifeast.com Online ordering from hundreds of LA delivery and carryout restaurants

I've just started using LLVM for a project I'm working on, and the docs seem to encourage the use of alloca, with the expectation that various optimization passes will optimize away unnecessary stack pressure. However, I can't seem to figure out how LLVM can properly re-use stack space, since it doesn't know the extend of a stack variable. In this simple C example: extern void

Hi again. I have a complex type system in my custom language that isn't easily representable as LLVM IR types, so I figured I could mostly get along with treating my types as i8* and doing the appropriate bitcasts and inttoptr instructions, and doing pointer arithmetic myself (by casting the pointers to ints, adding the appropriate byte offsets, and then casting back to pointers). However,