Re: [patch] Input cleanups for 2.5.29 [2/2]

Andreas Schwab (schwab@suse.de)
Wed, 31 Jul 2002 14:57:29 +0200


Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

|> On Tue, 2002-07-30 at 22:55, Ben Pfaff wrote:
|> > 1 The typedef name intN_t designates a signed integer type with
|> > width N, no padding bits, and a two's complement
|> > representation. Thus, int8_t denotes a signed integer type
|> > with a width of exactly 8 bits.
|>
|> And arbitary alignment requirements. At least I see nothing in C99
|> saying that
|>
|> uint8_t foo;
|> uint8_t bar;
|>
|> isnt allowed to give you interesting suprises

If it's part of a structure, then yes. The C standard has always allowed
arbitrary padding between structure members. It's an ABI issue.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/