Bug#501741: marked as done ([linux-2.6] Unset the "Optimize for size" config option (CONFIG_CC_OPTIMIZE_FOR_SIZE))
Your message dated Fri, 10 Oct 2008 02:57:39 +0200
with message-id <20081010005739.GU10015@baikonur.stro.at>
and subject line Re: Bug#501741: [linux-2.6] Unset the "Optimize for size" config option (CONFIG_CC_OPTIMIZE_FOR_SIZE)
has caused the Debian Bug report #501741,
regarding [linux-2.6] Unset the "Optimize for size" config option (CONFIG_CC_OPTIMIZE_FOR_SIZE)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
501741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501741
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: linux-2.6
Severity: wishlist
According to a kernel config file from the current Lenny's 2.6.26 AMD64 kernel, the CONFIG_CC_OPTIMIZE_FOR_SIZE option
was set to "y" when this kernel was compiled, which means the optimization for code size instead of speed was chosen.
According to that option's description, it means that the "-Os" option will be passed to the compiler instead of "-O2".
That option disables many of the more advanced optimizations. Documentation on gcc gives the impression that such option
basically says, "I do not care about performance at all, just make the code as small as possible".
While saving 100-200 KB on kernel could be useful in times of machines which had 8-16 MBs of RAM, I think this is no
longer the most reasonable choice currently. Given average amounts of RAM in today's computers, losing the possible
performance advantage in favor of a couple of tens or hundreds KBs of memory seems is no longer a good trade-off. I hope
you consider unsetting that option.
With respect,
Roman.
--- End Message ---
--- Begin Message ---
On Fri, Oct 10, 2008 at 05:25:35AM +0600, Roman Mamedov wrote:
> Source: linux-2.6
> Severity: wishlist
>
> According to a kernel config file from the current Lenny's 2.6.26 AMD64 kernel, the CONFIG_CC_OPTIMIZE_FOR_SIZE option
> was set to "y" when this kernel was compiled, which means the optimization for code size instead of speed was chosen.
>
> According to that option's description, it means that the "-Os" option will be passed to the compiler instead of "-O2".
> That option disables many of the more advanced optimizations. Documentation on gcc gives the impression that such option
> basically says, "I do not care about performance at all, just make the code as small as possible".
>
> While saving 100-200 KB on kernel could be useful in times of machines which had 8-16 MBs of RAM, I think this is no
> longer the most reasonable choice currently. Given average amounts of RAM in today's computers, losing the possible
> performance advantage in favor of a couple of tens or hundreds KBs of memory seems is no longer a good trade-off. I hope
> you consider unsetting that option.
unless you come up with a benchmark *showing* a huge difference,
such a change will not be considered, thus closing.
--- End Message ---
Reply to: