From: Andi Kleen <andi@firstfloor.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"Keith A. Prickett" <keithp@marvell.com>,
linux-kernel@vger.kernel.org
Subject: Re: Building Kernel with -O0
Date: Tue, 9 Sep 2008 22:05:17 +0200 [thread overview]
Message-ID: <20080909200517.GE7714@one.firstfloor.org> (raw)
In-Reply-To: <20080909194305.GG30160@cs181140183.pp.htv.fi>
> > I think a few more cases crept in where it was common to write
> > build time asserts as
> >
> > if (some condition the compiler evaluates at runtime)
> ^^^^^^^
> buildtime
Thank for the correction.
>
> > __error_condition_xyz_is_false();
> >
> > and this obviously relies on the optimizer to build. But these
> > are all slowly moving over the BUILD_BUG_ON() which also doesn't
> > rely on the optimizer, so it's also obsolete.
> >...
>
> The reason why it works for Keith at all seems to be that even with -O0
> gcc already does this kind of optimizations.
What I mean is global optimization over the whole function, like
constant propagation. That is required for some of the more complex
macros like the *_user() ones.
Some expression evaluation is required by the C standard (e.g.
otherwise you couldn't generally declare global arrays with expressions)
While that's technically not required in the body of the function
outside declarations the compiler does it normally. But only inside
a statement.
-Andi
next prev parent reply other threads:[~2008-09-09 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 17:50 Building Kernel with -O0 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 [this message]
2008-09-09 22:24 ` David Howells
2008-09-25 13:31 ` Adrian Bunk
2008-09-25 13:51 ` David Howells
[not found] <fa.NLANnOwj/8iuI5QjLt63gFrBDJA@ifi.uio.no>
2008-09-04 23:40 ` Robert Hancock
[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 ` 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)
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=20080909200517.GE7714@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=bunk@kernel.org \
--cc=keithp@marvell.com \
--cc=linux-kernel@vger.kernel.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