Re: Use of C99 int types

[Kyle Moffett]

On Apr 03, 2005, at 16:25, Kenneth Johansson wrote:
> But is this not exactly what Dag Arne Osvik was trying to do ??
> uint_fast32_t means that we want at least 32 bits but it's OK with
> more if that happens to be faster on this particular architecture.
> The problem was that the C99 standard types are not defined anywhere
> in the kernel headers so they can not be used.

Uhh, so what's wrong with "int" or "long"?  On all existing archs
supported by linux, "int" is 32 bits, "long long" is 64 bits, and
"long" is an efficient word-sized value that can hold a casted
pointer.  I suppose it's theoretical that linux could be ported to
some arch where int is 16 bits, but so much stuff implicitly depends
on at least 32-bits in int that I think that's unlikely.  GCC will
generally do the right thing if you just tell it "int".

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r  
!y?(-)
------END GEEK CODE BLOCK------


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/