Warning: DOMDocument::loadXML() [function.DOMDocument-loadXML]: PCDATA invalid Char value 20 in Entity, line: 54 in /srv/lkml.org/scripts/getmail.php on line 208
Warning: XSLTProcessor::transformToXml() expects parameter 1 to be object, boolean given in /srv/lkml.org/scripts/getmail.php on line 211
This message generated a parse failure. Raw output follows here. Please use 'back' to navigate.
From devnull@lkml.org Fri Nov 21 18:57:04 2008
Received: from lml.valinux.com (postfix@lml.varesearch.com [209.81.8.228]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id DAA27320 for ; Fri, 7 Jan 2000 03:57:39 -0500 (EST)
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by lml.valinux.com (Postfix) with ESMTP id 5307268F3D; Thu, 6 Jan 2000 19:10:46 -0800 (PST)
Received: by vger.rutgers.edu via listexpand id ; Thu, 6 Jan 2000 21:46:44 -0500
Received: by vger.rutgers.edu id ; Thu, 6 Jan 2000 20:59:15 -0500
Received: from kullstam.ne.mediaone.net ([24.218.92.14]:1058 "HELO kullstam.ne.mediaone.net") by vger.rutgers.edu with SMTP id ; Thu, 6 Jan 2000 20:53:40 -0500
Received: (qmail 843 invoked by uid 501); 7 Jan 2000 01:53:23 -0000
From: "Johan Kullstam"
To: Thierry Vignaud
Cc: Jesse Pollard , linux-kernel@vger.rutgers.edu
Subject: Re: time_t size: The year 2038 bug?
References: <200001061351.HAA79315@tomcat.admin.navo.hpc.mil> <3874BBAE.1C4DB5C2@mandrakesoft.com>
Organization: none
Date: 06 Jan 2000 20:53:23 -0500
In-Reply-To: Thierry Vignaud's message of "Thu, 06 Jan 2000 16:58:38 +0100"
Message-Id:
Lines: 42
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-linux-kernel@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-kernel-outgoing-dig
Thierry Vignaud writes:
> Jesse Pollard a écrit :
> >
> > Johan Kullstam"
> > >i'd also like to see C types with *specified* bit widths, e.g.,
> > >int16, int32, uint8 &c. then you could write more portable code when
> > >you really need a certain number of bits like for CRC algorithms.
>
> ever head of inttypes.h ???
consider a 64 bit processor where you'd like to have 64 bit integers.
use the following:
type bits
char 8
short int 16
int 64
long int 64
long long 128
ok now that we have no 32 bit integer quantity, please get me a 32 bit
integer using a #define macro.
therefore, we are forced to do
type bits
char 8
short int 16
int 32 (or 16)
long int 64 (or 32)
long long 128 (or 64)
in order to cover 8, 16 and 32. there is no way to have a 64 bit int
and cover all the smaller integers. you run out of types.
and how does inttypes.h help me on a pdp-10 with 36 bit integers?
--
J o h a n K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/