From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org,
pantelis.antoniou@gmail.com, linuxppc-embedded@ozlabs.org
Subject: Re: cpu features testing 32 vs 64 bit
Date: Thu, 8 Sep 2005 17:48:58 -0400 [thread overview]
Message-ID: <f2ea45e1b2a9689c450811a61ed46183@embeddededge.com> (raw)
In-Reply-To: <D8DEC759-EAB9-457F-AF7B-A10D6593B27A@freescale.com>
On Sep 8, 2005, at 5:20 PM, Kumar Gala wrote:
>>> if (!cpu_has_feature(CPU_FTR_COHERENT_ICACHE))
>>> __flush_icache_range(start, stop);
>>> }
If we #define CPU_FTR_xxx as a 0 or all 1's for processors that have
or don't have these features, will the compiler be smart enough to
recognize an always true or false condition and remove the
test (or code as appropriate)?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-09-08 21:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 21:02 cpu features testing 32 vs 64 bit Becky Bruce
2005-09-08 21:08 ` Pantelis Antoniou
2005-09-08 21:20 ` Kumar Gala
2005-09-08 21:48 ` Dan Malek [this message]
2005-09-08 22:02 ` Kumar Gala
2005-09-08 22:20 ` Dan Malek
2005-09-08 22:36 ` Arnd Bergmann
2005-09-09 0:08 ` David Gibson
2005-09-09 4:23 ` [PATCH] powerpc: merge include/asm/cputable.h Arnd Bergmann
2005-09-14 19:11 ` Kumar Gala
2005-09-14 23:58 ` Arnd Bergmann
2005-09-15 17:44 ` Kumar Gala
2005-09-15 22:56 ` Arnd Bergmann
2005-09-16 2:22 ` Kumar Gala
2005-09-16 3:11 ` Arnd Bergmann
2005-09-16 21:40 ` Kumar Gala
2005-09-17 0:36 ` Arnd Bergmann
2005-09-09 22:19 ` cpu features testing 32 vs 64 bit Benjamin Herrenschmidt
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=f2ea45e1b2a9689c450811a61ed46183@embeddededge.com \
--to=dan@embeddededge.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=pantelis.antoniou@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;
as well as URLs for NNTP newsgroup(s).