From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Help text for config OPTIMIZE_INLINING
Date: Sat, 11 Oct 2008 06:30:08 -0700 (PDT) [thread overview]
Message-ID: <537458.72510.qm@web38204.mail.mud.yahoo.com> (raw)
The main help text for the OPTIMIZE_INLINING kconfig option says:
"The gcc 4.x series have a rewritten inlining algorithm and disabling this option will generate a smaller kernel there."
That suggests that to generate a smaller kernel one should set the option to n. However the short text says:
"Allow gcc to uninline functions marked 'inline'"
While suggests that one should set it to y to generate smaller kernels. My own experience says that setting it to y DOES generate a smaller kernel so perhaps the main text should be changed to reflect this?
Sitsofe | http://sucs.org/~sits/
next reply other threads:[~2008-10-11 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 13:30 Sitsofe Wheeler [this message]
2008-10-11 14:36 ` Help text for config OPTIMIZE_INLINING Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-10-11 19:05 Sitsofe Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=537458.72510.qm@web38204.mail.mud.yahoo.com \
--to=sitsofe@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox