From: Jesper Juhl <jj@chaosbits.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Daniel Lezcano <daniel.lezcano@free.fr>,
Eric Paris <eparis@redhat.com>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kbuild@vger.kernel.org
Subject: PATCH][RFC][resend] CC_OPTIMIZE_FOR_SIZE should default to N
Date: Mon, 21 Mar 2011 21:08:24 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1103212105490.15815@swampdragon.chaosbits.net> (raw)
I believe that the majority of systems we are built on want a -O2 compiled
kernel. Optimizing for size (-Os) is mainly benneficial for embedded
systems and systems with very small CPU caches (correct me if I'm wrong).
So it seems wrong to me that CC_OPTIMIZE_FOR_SIZE defaults to 'y' and
recommends saying 'Y' if unsure. I believe it should default to 'n' and
recommend that if unsure. People who bennefit from -Os know who they are
and can enable the option if needed/wanted - the majority shouldn't
select this. Right?
Signed-off-by: Jesper Juhl <jj@chaosbits.net>
---
Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index 56240e7..0d63dfa 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -903,12 +903,12 @@ endif
config CC_OPTIMIZE_FOR_SIZE
bool "Optimize for size"
- default y
+ default n
help
Enabling this option will pass "-Os" instead of "-O2" to gcc
resulting in a smaller kernel.
- If unsure, say Y.
+ If unsure, say N.
config SYSCTL
bool
--
Jesper Juhl <jj@chaosbits.net> http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.
next reply other threads:[~2011-03-21 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 20:08 Jesper Juhl [this message]
2011-03-22 2:52 ` PATCH][RFC][resend] CC_OPTIMIZE_FOR_SIZE should default to N Steven Rostedt
2011-03-22 8:21 ` Pekka Enberg
2011-03-22 8:25 ` Jesper Juhl
2011-03-22 10:27 ` Ingo Molnar
2011-03-22 16:59 ` Linus Torvalds
2011-03-23 17:45 ` Andi Kleen
2011-03-23 21:14 ` Ingo Molnar
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=alpine.LNX.2.00.1103212105490.15815@swampdragon.chaosbits.net \
--to=jj@chaosbits.net \
--cc=akpm@linux-foundation.org \
--cc=daniel.lezcano@free.fr \
--cc=eparis@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=zippel@linux-m68k.org \
/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;
as well as URLs for NNTP newsgroup(s).