From owner-freebsd-hackers Mon Nov 10 21:30:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA26907 for hackers-outgoing; Mon, 10 Nov 1997 21:30:12 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA26900 for ; Mon, 10 Nov 1997 21:30:07 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id WAA22034; Mon, 10 Nov 1997 22:30:05 -0700 (MST) From: Terry Lambert Message-Id: <199711110530.WAA22034@usr02.primenet.com> Subject: Re: Newest Pentium bug (fatal) To: archie@whistle.com (Archie Cobbs) Date: Tue, 11 Nov 1997 05:30:03 +0000 (GMT) Cc: cmott@srv.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199711102243.OAA00849@bubba.whistle.com> from "Archie Cobbs" at Nov 10, 97 02:43:54 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This brings up a good point... if you're writing code and you > want/expect something to be 32 bits, then its type should be > either "int32_t" or "u_int32_t"!! Same goes for 8, 16, and 64! > > You're going to kill me on this... ;-). I suppose: 8 char 16 short 32 int 64 long ? ...I thought "int" was supposed to be the single-cycle-fetch type... so isn't int 64 like long? If so, how do I get an int32_t? Anyway, damn ANSI for not implementing sized types... or adopting "quad" and loosening the restriction on sizeof(long)>=sizeof(int). 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.