Richard Purdie wrote:
> The kernel uses UINT_MAX defined from kernel.h in a variety of places.
>
> While looking at the behaviour of the LZO code, I noticed it seemed to
> think an int was 8 bytes large on my 32 bit i386 machine. It isn't but
> why did it think that?
>
> kernel.h says:
>
> #defi
Richard Purdie <[EMAIL PROTECTED]> writes:
> If I try to compile the code fragment below, I see the error:
>
> #define UINT_MAX (~0U)
> #if (0x == UINT_MAX)
> #error argh
> #endif
The preprocessor computes all expressions with the largest available
range. It does not know
> The kernel uses UINT_MAX defined from kernel.h in a variety of places.
>
> While looking at the behaviour of the LZO code, I noticed it seemed to
> think an int was 8 bytes large on my 32 bit i386 machine. It isn't but
> why did it think that?
>
> kernel.h says:
>
> #define INT_MAX
The kernel uses UINT_MAX defined from kernel.h in a variety of places.
While looking at the behaviour of the LZO code, I noticed it seemed to
think an int was 8 bytes large on my 32 bit i386 machine. It isn't but
why did it think that?
kernel.h says:
#define INT_MAX ((int)(~0U>>1))
#defi
4 matches
Mail list logo