From: Linus Torvalds <torvalds@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [2.6 patch] offer CC_OPTIMIZE_FOR_SIZE only if EXPERIMENTAL
Date: Wed, 14 Dec 2005 14:36:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0512141429030.3292@g5.osdl.org> (raw)
In-Reply-To: <20051214221304.GE23349@stusta.de>
On Wed, 14 Dec 2005, Adrian Bunk wrote:
>
> What about marking it as EXPERIMENTAL?
It's not experimental on other architectures, where it is always used.
The best option _may_ be to do something like this, where we use that
"depends on" to set the expectations, and people shouldn't see it unless
they ask for EXPERIMENTAL.
It also refuses to turn on for SPARC64, since that seems to be known
broken. Or should it be just "SPARC"? Davem?
Linus
---
diff --git a/init/Kconfig b/init/Kconfig
index be74adb..6c5dbed 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -256,6 +256,20 @@ config CPUSETS
source "usr/Kconfig"
+config CC_OPTIMIZE_FOR_SIZE
+ bool "Optimize for size (Look out for broken compilers!)"
+ default y
+ depends on ARM || H8300 || EXPERIMENTAL
+ depends on !SPARC64
+ help
+ Enabling this option will pass "-Os" instead of "-O2" to gcc
+ resulting in a smaller kernel.
+
+ WARNING: some versions of gcc may generate incorrect code with this
+ option. If problems are observed, a gcc upgrade may be needed.
+
+ If unsure, say N.
+
menuconfig EMBEDDED
bool "Configure standard kernel features (for small systems)"
help
@@ -338,18 +352,6 @@ config EPOLL
Disabling this option will cause the kernel to be built without
support for epoll family of system calls.
-config CC_OPTIMIZE_FOR_SIZE
- bool "Optimize for size"
- default y if ARM || H8300
- help
- Enabling this option will pass "-Os" instead of "-O2" to gcc
- resulting in a smaller kernel.
-
- WARNING: some versions of gcc may generate incorrect code with this
- option. If problems are observed, a gcc upgrade may be needed.
-
- If unsure, say N.
-
config SHMEM
bool "Use full shmem filesystem" if EMBEDDED
default y
next prev parent reply other threads:[~2005-12-14 22:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 19:10 [2.6 patch] fix the EMBEDDED menu Adrian Bunk
2005-12-14 22:05 ` Andrew Morton
2005-12-14 22:13 ` [2.6 patch] offer CC_OPTIMIZE_FOR_SIZE only if EXPERIMENTAL Adrian Bunk
2005-12-14 22:18 ` Jesper Juhl
2005-12-14 22:28 ` Jesper Juhl
2005-12-15 0:40 ` Dave Jones
2005-12-15 5:24 ` David S. Miller
2005-12-15 15:01 ` Krzysztof Halasa
2005-12-15 17:35 ` Dave Jones
[not found] ` <7c3341450601191017o796faf45r2cc5c8e544dcfe11@mail.gmail.com>
2006-01-19 19:13 ` Dave Jones
2005-12-15 19:20 ` Denis Vlasenko
2005-12-14 22:22 ` Andrew Morton
2005-12-14 22:26 ` Adrian Bunk
2005-12-14 22:30 ` Russell King
2005-12-14 22:36 ` Linus Torvalds [this message]
2005-12-14 22:44 ` Adrian Bunk
2005-12-14 22:46 ` Adrian Bunk
2005-12-14 23:32 ` Linus Torvalds
2005-12-14 23:43 ` Adrian Bunk
2005-12-15 6:45 ` David S. Miller
2005-12-14 23:48 ` David S. Miller
2006-01-19 17:59 ` Eric Lammerts
2005-12-14 22:17 ` [2.6 patch] fix the EMBEDDED menu Russell King
2005-12-14 22:24 ` Adrian Bunk
2005-12-17 21:20 ` Nicolas Pitre
2005-12-15 13:01 ` Rogério Brito
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=Pine.LNX.4.64.0512141429030.3292@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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).