Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!cs.umn.edu!kksys!edgar!orac!bret
From: bret@orac.UUCP (Bret Indrelee)
Newsgroups: comp.lang.c
Subject: Re: 64 bit architectures and C/C++
Summary: driver writers want to know
Message-ID: <314@orac.UUCP>
Date: 19 May 91 19:55:21 GMT
Article-I.D.: orac.314
References: <168@shasta.Stanford.EDU> <45690005@hpcupt3.cup.hp.com> <16103@smoke.brl.mil>
Organization: Technix Inc., Saint Paul MN, USA
Lines: 17

In article <16103@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>
>By the way, there is NO NEED to say what data size choices a 64-bit
>implementation "should" make.  It "should" not matter to any sensible
>application.



Except maybe the guy writing a device driver, where the person needs
to exactly match the size of a data type to the size of a hardware
register.  Yet another reason to spread the sizes around.

-Bret
-- 
------------------------------------------------------------------------------
Bret Indrelee		|	<This space left intentionally blink>
bret@orac.edgar.mn.org	|					;^)