From: David Garfield <garfield@irving.iisd.sra.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org, andersen@codepoet.org,
Matthew Wilcox <willy@debian.org>
Subject: Re: kernel header separation
Date: Mon, 8 Sep 2003 17:05:58 -0400 [thread overview]
Message-ID: <16220.61238.347537.307965@irving.iisd.sra.com> (raw)
In-Reply-To: <20030908223409.B1085@pclin040.win.tue.nl>
Andries Brouwer writes:
> On Mon, Sep 08, 2003 at 04:23:18PM -0400, David Garfield wrote:
>
> > On the other hand, the ISO C99 definition is probably something like:
> > an integral type capable of storing the values 0 through 255
> > inclusive. (ok, I don't have a copy of the new standard but I have
> > seriously examined the old one.) I would not count on uint8_t
> > necessarily being unsigned on unusual hardware.
>
> Why do you come with FUD and speculation when it is so easy
> to check the facts?
>
> "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.
>
> The typedef name uintN_t designates an unsigned integer type with width N.
> Thus, uint24_t denotes an unsigned integer type with a width of exactly 24 bits.
>
> These types are optional. However, if an implementation provides integer types with
> widths of 8, 16, 32, or 64 bits, it shall define the corresponding typedef names."
1) It was not my intent to produce FUD, and speculation is because I
understood this was not a freely available standard (it can be
found at http://anubis.dkuug.dk/JTC1/SC22/WG14/www/standards ).
2) I have now downloaded and read some of this standard. You do
realize that a uint16_t can take 32 bits, don't you? (Hint: reread
section 6.2.6.2 for the definition of width.)
3) There is still the issue that these types are not guaranteed to
exist, as you have quoted. Also the issue that what Linux
guarantees for these types is not specified.
--David Garfield
next prev parent reply other threads:[~2003-09-08 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 19:16 Matthew Wilcox
2003-09-03 1:49 ` Erik Andersen
2003-09-05 14:36 ` David Woodhouse
2003-09-05 21:10 ` Erik Andersen
2003-09-05 14:41 ` Matthew Wilcox
2003-09-05 21:16 ` Erik Andersen
2003-09-05 23:22 ` Matthew Wilcox
2003-09-08 13:38 ` David Woodhouse
2003-09-08 14:12 ` Alan Cox
2003-09-08 14:25 ` Jeff Garzik
2003-09-08 14:31 ` Alan Cox
2003-09-08 14:32 ` Jeff Garzik
2003-09-08 14:42 ` Matthew Wilcox
2003-09-08 15:22 ` Andreas Schwab
2003-09-08 14:37 ` Andreas Schwab
2003-09-08 20:23 ` David Garfield
2003-09-08 20:34 ` Andries Brouwer
2003-09-08 21:05 ` David Garfield [this message]
2003-09-08 20:43 ` Erik Andersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16220.61238.347537.307965@irving.iisd.sra.com \
--to=garfield@irving.iisd.sra.com \
--cc=aebr@win.tue.nl \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®