From: Robert Hancock <hancockr@shaw.ca>
To: "Keith A. Prickett" <keithp@marvell.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Building Kernel with -O0
Date: Thu, 04 Sep 2008 17:40:51 -0600 [thread overview]
Message-ID: <48C07203.1090706@shaw.ca> (raw)
In-Reply-To: <fa.NLANnOwj/8iuI5QjLt63gFrBDJA@ifi.uio.no>
Keith A. Prickett wrote:
> I was looking at some changes to the 2.6.26.y kernel in "compiler-gcc.h"
> and had some questions.
> ( http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.26.y.git;a=commitdiff;h=ae3a0064e6d69068b1c9fd075095da062430bda9 )
>
> I was attempting to cross-compile Linux for a Marvell core with
> Optimizations turned off and ran across an error due to the
> __attribute__((always_inline)) attribute.
>
> It looks like the default behavior used to always have this feature on,
> but Ingo committed some changes that allows this behavior to be turned
> off (With the correct Kconfig file changes).
>
> I'm VERY new to Linux but was wondering if there was a way (config
> option) to turn this inline attribute off in previous versions of the
> kernel besides these new macros. It seems building with optimization
> level 0 should be a natural thing for kernel driver developers to do for
> debugging purposes.
>
> In summary: I want to compile with optimizations off and the compile is
> failing now when I try this. How can this be resolved?
I don't think this has ever been supported. Even in current kernels
where the compiler is not always forced to inline all functions, I
believe there are some functions that need to be inlined and still use
forced inlining, and if no optimizations are enabled, no inlining can be
done.
next parent reply other threads:[~2008-09-04 23:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.NLANnOwj/8iuI5QjLt63gFrBDJA@ifi.uio.no>
2008-09-04 23:40 ` Robert Hancock [this message]
[not found] <b8rB2-6BM-1@gated-at.bofh.it>
[not found] ` <badXc-7gl-21@gated-at.bofh.it>
[not found] ` <baf2M-bE-7@gated-at.bofh.it>
[not found] ` <bagBJ-20J-7@gated-at.bofh.it>
2008-09-10 11:52 ` Building Kernel with -O0 Bodo Eggert
2008-09-12 5:21 ` emin ak
2008-09-12 13:23 ` linux-os (Dick Johnson)
2008-09-12 14:45 ` linux-os (Dick Johnson)
2008-09-04 17:50 Keith A. Prickett
2008-09-09 16:04 ` Adrian Bunk
2008-09-09 17:10 ` Keith A. Prickett
2008-09-09 18:55 ` linux-os (Dick Johnson)
2008-09-09 19:24 ` Andi Kleen
2008-09-09 19:43 ` Adrian Bunk
2008-09-09 20:05 ` Andi Kleen
2008-09-09 22:24 ` David Howells
2008-09-25 13:31 ` Adrian Bunk
2008-09-25 13:51 ` David Howells
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=48C07203.1090706@shaw.ca \
--to=hancockr@shaw.ca \
--cc=keithp@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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