Re: static functions are your friends (Was GPIO revisited)

[Thor Lancelot Simon <tls%panix.com@localhost>]

On Sun, Aug 09, 2009 at 03:30:12PM +0000, YAMAMOTO Takashi wrote:
> hi,
> 
> > I took the time to write a function that crahses the kernel on  
> > purpose.  Compiled as non static function, ddb showed me the function  
> > name and function call trace with proper function names.  Quite easy  
> > to locate the faulty spot.  To complete my test, I compiled the very  
> > same code with all functions declared static.  Now the ddb trace does  
> > not show me the function names, making it a lot harder to locate the  
> > faulty spot.
> 
> you want __noinline?

I think so, yeah.  But maybe we need another macro which does 'static'
either way, but only does __noinline if !DIAGNOSTIC (or !DEBUG)?  I think
that is approximately what Marc wants.

Thor