Re: C function stack and core local memory
Posted: Tue Aug 06, 2013 2:39 amMike,
Usually, it is best to just compile a C function that handles many (>4) inputs and uses them all to calculate something - say, their sum - and return this calculation result. Then, look at the generated assembly (e-objdump -D) and see how the compiler does it. You should compile w/o optimization to really see how the stack works.
Usually, it is best to just compile a C function that handles many (>4) inputs and uses them all to calculate something - say, their sum - and return this calculation result. Then, look at the generated assembly (e-objdump -D) and see how the compiler does it. You should compile w/o optimization to really see how the stack works.
