From: Benjamin LaHaise <bcrl@kvack.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the CONFIG_CC_ALIGN_* options
Date: Sun, 12 Feb 2006 16:40:46 -0500 [thread overview]
Message-ID: <20060212214046.GA20477@kvack.org> (raw)
In-Reply-To: <20060212174802.GJ30922@stusta.de>
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
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?
-ben
next prev parent reply other threads:[~2006-02-12 21:45 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 [this message]
2006-02-12 23:16 ` Adrian Bunk
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=20060212214046.GA20477@kvack.org \
--to=bcrl@kvack.org \
--cc=bunk@stusta.de \
--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