Re: [patch 00/2] improve .text size on gcc 4.0 and newer compilers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


* Linus Torvalds <[email protected]> wrote:

> > For example, I add "inline" for static functions which are only called
> > from one place.
> That's actually not a good practice. Two reasons:
>  - debuggability goes way down. Oops reports give a much nicer call-chain 
>    and better locality for uninlined code.

yes, and to improve debuggability, i often do this at the top of 
debugged .c modules:

	#undef inline
	#define inline

to get good stacktraces. So debuggability is i think another argument to 
further decouple 'inline' from 'always inline' - so a global .config 
DEBUG_ option could turn all inlines into real function calls. (we 
already have CONFIG_FRAME_POINTERS to improve stack-trace output, at the 
price of slightly slower code.)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at
Please read the FAQ at

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux