Re: 64-bit

Article View: comp.sys.powerpc

Article #15

#15

From: Chris Jones
Date: Mon, 13 Nov 1995 14:32

13 lines
1253 bytes

In article <483pe6$aft@spool.cs.wisc.edu> tuc@.cs.wisc.edu (Brian Cole) writes:

   I'm confused as to why a compiler writer would make a new "long long" type
   instead of making "long" be a 64-bit integer.  That way "char", "short",
   "int", and "long" would be 1, 2, 4, and 8-byte integers, respectively,
   and coders could stick to legal ANSI C.  I've been waiting for C compilers
   to make this switch for a few years now.

Kendall Square Research's C compiler used this scheme.  One thing we (I was at
KSR for nearly 7 years) found was that there is a lot of code which "knows"
that pointers can fit into ints, and that wasn't true on KSR machines.
-- 
Chris Jones    clj@bbn.com

Technical Details

Message-ID: <rpfbuqg1t7g.fsf@unicorn.bbn.com>

Path: arc1-ca.pugleaf.net!info-server.bbn.com!news

References: <MEISSNER.95Nov9091407@tiktok.cygnus.com> <47tbel$tta@rs18.hrz.th-darmstadt.de> <483pe6$aft@spool.cs.wisc.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!info-server.bbn.com!news
From: Chris Jones <clj@bbn.com>
Newsgroups: comp.sys.powerpc,comp.lang.c
Subject: Re: 64-bit
Date: 13 Nov 1995 09:32:03 -0500
Organization: BBN Systems and Technologies Division
Sender: clj@unicorn.bbn.com
Message-ID: <rpfbuqg1t7g.fsf@unicorn.bbn.com>
References: <MEISSNER.95Nov9091407@tiktok.cygnus.com>
 <47tbel$tta@rs18.hrz.th-darmstadt.de> <483pe6$aft@spool.cs.wisc.edu>
NNTP-Posting-Host: unicorn.bbn.com
In-reply-to: tuc@.cs.wisc.edu's message of 12 Nov 1995 03:24:54 GMT
X-Newsreader: Gnus v5.0.9

Reply to Parent Message