public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the CONFIG_CC_ALIGN_* options
Date: Mon, 13 Feb 2006 00:16:21 +0100	[thread overview]
Message-ID: <20060212231618.GM30922@stusta.de> (raw)
In-Reply-To: <20060212214046.GA20477@kvack.org>

On Sun, Feb 12, 2006 at 04:40:46PM -0500, Benjamin LaHaise wrote:
> On Sun, Feb 12, 2006 at 06:48:02PM +0100, Adrian Bunk wrote:
> > I don't see any use case for the CONFIG_CC_ALIGN_* options:
> > - they are only available if EMBEDDED
> > - people using EMBEDDED will most likely also enable 
> >   CC_OPTIMIZE_FOR_SIZE
> > - the default for -Os is to disable alignment
> 
> CONFIG_EMBEDDED should actually be spell CONFIG_ADVANCED.  Not everyone 

We need both with CONFIG_EMBEDDED depending on CONFIG_ADVANCED (see my 
other email).

> testing different alignments is building an embedded system targetted for 
> size.  The option is just as useful in doing performance comparisons.  
> Besides, is it really a maintenence load?

It is not a maintenence load, but does it make sense to offer this in 
any way to _users_?

gcc already sets this options with -Os/-O2.

We do already override the choice of gcc in some cpu specific cases.

If someone is doing performance comparisons and discovers that the 
default settings gcc chooses aren't good, the only sane thing is to 
discuss whether it makes sense to change this.

> 		-ben

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2006-02-12 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 17:48 [RFC: 2.6 patch] remove the CONFIG_CC_ALIGN_* options Adrian Bunk
2006-02-12 21:40 ` Benjamin LaHaise
2006-02-12 23:16   ` Adrian Bunk [this message]

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=20060212231618.GM30922@stusta.de \
    --to=bunk@stusta.de \
    --cc=bcrl@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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