search for: tp24093351p24095072

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

2009 Jun 18
0
[LLVMdev] Explicitly Freeing Allocas
Nyx wrote: > Hello, > > I would just like to ask if it's possible to explicitly free allocas. This > is because I need to call functions that take structs of different sizes as > input, (possibly inside of loops) and I would rather avoid a stack overflow. You can't explicitly free a specific alloca, but you can use the llvm.stacksave and llvm.stackrestore intrinsics to
2009 Jun 18
1
[LLVMdev] Explicitly Freeing Allocas
...e > _______________________________________________ > 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://www.nabble.com/Explicitly-Freeing-Allocas-tp24093351p24095072.html Sent from the LLVM - Dev mailing list archive at Nabble.com.
2009 Jun 18
5
[LLVMdev] Explicitly Freeing Allocas
Hello, I would just like to ask if it's possible to explicitly free allocas. This is because I need to call functions that take structs of different sizes as input, (possibly inside of loops) and I would rather avoid a stack overflow. If this is not possible, an alternate solution would be for me to allocate an array of bytes larger than all the struct types I may be using, and cast that