[GD-Windows] autodocument max stack usage

[Corrinne Y. <cor...@sp...>]

Is there a way to make Visual C linker output the maximum stack allocation
(including local stack locks and unlocks within function calls) of an entire
linked executable?

I had written an autodocumentation tool that parses source code of all the
modules and generate a worst case estimate of stack usage report. It is
quite accurate for C modules, it works on even local stacks inside
functions, and has trouble estimating stack and memory usage for C++ classes
as there are hidden stack locks and allocations during instantiations and
even executions (if one steps into the assembly and watch all the stack
locks).

Given the compiler and linker would need to know the executable's stack
usage better than a programmer like myself would, I suspect this information
I seek (interactively) should be spittable by the compiler and linker
somewhere.