[ Charset UTF-8 unsupported, converting... ] > On 12/12/2017 19:01, Rodney W. Grimes wrote: > > We should probably start looking for those, something someone who is > > offerring help but doesnt know what they might be good at, but can > > read C code. They could be utililized t simply scan through the > > code looking for this type of thing and bring it to the attention > > of a area of expertise commiter. > > By the way, there are tools that can analyze binary code (e.g. a kernel binary > or a module) and determine stack requirements of each function. I think that > debug symbols might be required too.
That would be an even better first start, even if it just could tell us what the local var stack space request of each function was that might point out some easly low hanging fruit. Can it also tell us how big the call frame is? > > I am not sure if there are tools that can analyze stack requirements for > possible call chains rather than individual functions. Call graphs can be used to find deep chains. Combine the above with a call graph and we should be able to come up with some data. This also sounds like a good caniate for GSOC, creation of a call graph with static analysis of local variable size + call frame size requirements as a O(1) stack space estimator. -- Rod Grimes rgri...@freebsd.org _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
