On 26 Aug 2016, at 03:21, Andrew Keller <andrew@kellerfarm.com> wrote:
Perhaps that’s the machine code that pushes the function's local variables onto the stack?
Most likely.
Is all memory required for all local variables in a given function allocated on the stack immediately upon invoking the function … ?
Yes. Well, it’s not /guaranteed/ to be that way—in most situations the exact mechanics of this is up to the compiler—but the general approach taken by most compilers is to adjust the stacker pointer once in the function prologue [1] and leave it there until the function returns.
A macro that allocates a 4KB array on the stack every time it’s used.
Yowsers! 4 KiB on a user stack is a lot; it’s crazy talk on a kernel stack (-:
Fortunately, that macro represents a goldmine of opportunities for improvement.
Yep. Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware [1] <https://en.wikipedia.org/wiki/Function_prologue> _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com