search for: sshumaker

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,

On Mon, Dec 14, 2009 at 12:27 PM, Scott Shumaker <sshumaker at gmail.com> wrote: > 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,...

Ahh, this states the problem precisely. Does anyone know if there is active development in this direction? I'd love to be able to use llvm.lifetime.start() / end(). Scott On Fri, Dec 11, 2009 at 12:12 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello, Scott > >> I've just started using LLVM for a project I'm working on, and the >> docs seem

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