From: Ingo Molnar <mingo@elte.hu>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH linux-tip] x86: Change OPTIMIZE_INLINING help to say enabling makes smaller kernels
Date: Wed, 22 Oct 2008 18:04:16 +0200 [thread overview]
Message-ID: <20081022160416.GO23060@elte.hu> (raw)
In-Reply-To: <20081011192753.GA13493@silver.sucs.org>
* Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
> The OPTIMIZE_INLINING help currently says "The gcc 4.x series have a
> rewritten inlining algorithm and disabling this option will generate a
> smaller kernel there."
>
> This contradicts other parts of the help text and my own tests:
> 5463127 2008-10-11 19:51 vmlinux.no-opt
> 5456152 2008-10-11 19:56 vmlinux.opt
>
> Reword text to say that enabling OPTIMIZE_INLINING will lead to smaller
> kernels with gcc 4.x or later.
>
> Signed-off-by: Sitsofe Wheeler <sitsofe@yahoo.com>
applied, thanks Sitsofe!
Ingo
prev parent reply other threads:[~2008-10-22 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 19:27 [PATCH linux-tip] x86: Change OPTIMIZE_INLINING help to say enabling makes smaller kernels Sitsofe Wheeler
2008-10-22 16:04 ` Ingo Molnar [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=20081022160416.GO23060@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
--cc=tglx@linutronix.de \
/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