From: Denis Vlasenko <vda@ilport.com.ua>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] offer CC_OPTIMIZE_FOR_SIZE only if EXPERIMENTAL
Date: Thu, 15 Dec 2005 21:20:01 +0200 [thread overview]
Message-ID: <200512152120.01271.vda@ilport.com.ua> (raw)
In-Reply-To: <9a8748490512141428q29f39ca5x66d2c52e22aa9208@mail.gmail.com>
On Thursday 15 December 2005 00:28, Jesper Juhl wrote:
> On 12/14/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> > On 12/14/05, Adrian Bunk <bunk@stusta.de> wrote:
> > > On Wed, Dec 14, 2005 at 02:05:31PM -0800, Andrew Morton wrote:
> > > > Adrian Bunk <bunk@stusta.de> wrote:
> > > > >
> > > > > Hi Linus,
> > > > >
> > > > > your patch to allow CC_OPTIMIZE_FOR_SIZE even for EMBEDDED=n has broken
> > > > > the EMBEDDED menu.
> > > >
> > > > It looks like that patch needs to be reverted or altered anyway. sparc64
> > > > machines are failing all over the place, possibly due to newly-exposed
> > > > compiler bugs.
> > > >
> > > > Whether it's the compiler or it's genuine kernel bugs, the same problems
> > > > are likely to bite other architectures.
> > >
> > > The help text already contains a bold warning.
> > >
> > > What about marking it as EXPERIMENTAL?
> > > That is not that heavy as EMBEDDED but expresses this.
> > >
> >
> > I, for one, definately think this is a good idea.
> > Actually, it boggles my mind what this is doing outside of EMBEDDED -
> > I just noticed it had moved when I build -git4 and oldconfig promted
> > me about it.
> >
> I should probably back this up with *why* it boggles my mind.
>
> -Os has been in EMBEDDED for ages, so it's not been tested by the
> majority of users with the wide range of compilers etc that people
> use. Putting it in as prominent a location as it occupies now means a
> *lot* of people are going to enable it and potentially get breakage -
> not good.
I always compile with -Os, not only kernel, but most of userspace.
So far no problems on i386 arch.
--
vda
next prev parent reply other threads:[~2005-12-15 19:20 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 [this message]
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
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=200512152120.01271.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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