search for: allocato

...kely to support the feature. That said, writing such as pass would be very easy to do. If you're only concerned about the size of stack-allocated objects, you can write an LLVM pass that looks for alloca instructions, determine that they are not in loops, and then sums up the sizes of the allocatoed memory using the DataLayout pass. If you want something that includes stack-spill slots and the like, then you'd need to write a MachineFunction Pass and examine the generated machine instructions. Alternatively, there might be a way in a MachineFunctionPass to get a pointer to a Machin...

Hi I was wondering if someone knows about any effort within the LLVM community to perform stack usage analysis per function similar to GCC's "-fstack-usage<http://gcc.gnu.org/onlinedocs/gnat_ugn_unw/Static-Stack-Usage-Analysis.html>" option? In short, with fstack-usage, gcc prints out the maximum stack usage per function (in bytes) which it can determine as a) static (no