Matthew Wilcox <[email protected]> writes:
> What do people think of CONFIG_64_BIT? It saves us from using
> !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or
> the X86_64 people deciding their architecture is more important.
>
> I also considered CONFIG_ILP32 vs CONFIG_LP64 (since that's the real
> problem with, eg, megaraid), but that requires more explanation and
> offers people several ways to get it wrong (should I depend on ILP32
> or !LP64?)
At least for code BITS_PER_LONG == 64 is already good enough.
For Kconfigs it may make sense, but is there any Config rule that
checks for all 64bit archs (opposed to checking for specific archs)?
I cannot thinkg of any.
-Andi
On Tue, Sep 02, 2003 at 07:35:11PM +0200, Andi Kleen wrote:
> Matthew Wilcox <[email protected]> writes:
>
> > What do people think of CONFIG_64_BIT? It saves us from using
> > !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or
>
> For Kconfigs it may make sense, but is there any Config rule that
> checks for all 64bit archs (opposed to checking for specific archs)?
> I cannot thinkg of any.
... that was what the patch added.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk