From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org, gdb@sourceware.org, hellogcc@freelists.org
Subject: Re: [PATCH] Built kernel without -O2 option
Date: Mon, 29 Nov 2010 19:06:00 -0000 [thread overview]
Message-ID: <20101129190546.GA14255@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTimewZ4QhxzL2vOYYV85pegy8Fu6Rb4XUAPqGUXS@mail.gmail.com>
On Mon, 29 Nov 2010 04:56:15 +0100, Hui Zhu wrote:
> So I make a patch that add a option in "Kernel hacking" called "Close
> GCC optimization". It will make kernel be built without -O2.
This seems to me as a workaround. The real fix would be to use
__attribute__((always_inline))
for functions requiring to be inlined and just compile everything with -O0 -g.
info '(gcc)Function Attributes'
`always_inline'
Generally, functions are not inlined unless optimization is specified.
For functions declared inline, this attribute inlines the function
even if no optimization level was specified.
But `always_inline' has been discussed on linux-kernel million times.
I have not googled out a resolution why it is not applicable to this problem,
do you know why?
Thanks,
Jan
next prev parent reply other threads:[~2010-11-29 19:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 3:56 Hui Zhu
2010-11-29 8:11 ` Américo Wang
2010-11-29 8:18 ` microcai
2010-11-29 8:25 ` Hui Zhu
[not found] ` <4CF36741.9000808@loongson.cn>
2010-11-29 8:48 ` [hellogcc] " Hui Zhu
2010-11-29 8:55 ` Steven
2010-11-29 8:58 ` Hui Zhu
[not found] ` <4CF3762B.9010102@loongson.cn>
2010-11-29 18:11 ` Valdis.Kletnieks
2010-11-29 18:35 ` Steven J. Magnani
[not found] ` <20101129220350.GA10923@core2.telecom.by>
2010-12-01 13:22 ` Hui Zhu
2010-12-01 12:23 ` bekars
2010-12-01 13:24 ` Hui Zhu
2010-12-01 13:58 ` bekars
2010-12-01 15:02 ` Hui Zhu
2010-12-01 15:42 ` jovi zhang
2010-11-29 8:48 ` Américo Wang
2010-11-29 9:11 ` Hui Zhu
2010-11-29 18:05 ` Valdis.Kletnieks
2010-11-29 20:51 ` richard -rw- weinberger
2010-11-29 21:00 ` Arnaud Lacombe
2010-11-29 21:07 ` richard -rw- weinberger
2010-11-29 9:44 ` Christian Borntraeger
2010-11-29 11:12 ` Segher Boessenkool
2010-11-29 11:17 ` Christian Borntraeger
2010-11-29 11:57 ` Nicholas Mc Guire
2010-12-01 12:18 ` Hui Zhu
2010-11-29 9:59 ` Andi Kleen
2010-11-29 10:12 ` Mark Wielaard
2010-11-30 9:26 ` Américo Wang
2010-11-30 18:40 ` Michael Snyder
2010-12-01 12:52 ` Hui Zhu
2010-11-29 19:06 ` Jan Kratochvil [this message]
2010-11-29 21:07 ` Arnaud Lacombe
2010-11-30 22:40 ` Petr Hluzín
2010-12-01 13:42 ` Hui Zhu
2010-12-01 13:11 ` Hui Zhu
2011-01-24 7:48 ` Hui Zhu
2011-01-24 8:11 ` Kevin Pouget
2011-01-24 12:42 ` Hui Zhu
2011-01-28 3:41 ` Hui Zhu
2011-02-17 2:44 ` Hui Zhu
[not found] ` <AANLkTik+beFdZZHLyei044q8EPHwvmiKoFAvAHsNuhmw@mail.gmail.com>
2011-02-21 12:52 ` Kevin Pouget
2011-02-23 5:20 ` Hui Zhu
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=20101129190546.GA14255@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=hellogcc@freelists.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teawater@gmail.com \
/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