On Sep 8, 2005, at 4:48 PM, Dan Malek wrote:
On Sep 8, 2005, at 5:20 PM, Kumar Gala wrote:
quoted
quoted
quoted
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)?
The compiler is smart enough in this case since cpu_has_feature() is
an inline function.
- kumar