Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!rutgers!clyde!watmath!watcgl!watmum!smvorkoetter
From: smvorkoetter@watmum.waterloo.edu (Stefan M. Vorkoetter)
Newsgroups: comp.lang.c
Subject: Re: C machine
Message-ID: <2802@watcgl.waterloo.edu>
Date: 2 Jan 88 18:16:39 GMT
References: <7535@alice.UUCP> <8226@steinmetz.steinmetz.UUCP> <461@auvax.UUCP> <163@bhjat.UUCP> <461@m10ux.UUCP>
Sender: daemon@watcgl.waterloo.edu
Reply-To: smvorkoetter@watmum.waterloo.edu (Stefan M. Vorkoetter)
Organization: U. of Waterloo, Ontario
Lines: 16

In article <461@m10ux.UUCP> rgr@m10ux.UUCP (Duke Robillard) writes:
>In article <163@bhjat.UUCP> bhj@bhjat.UUCP writes:
>>I hold that a short is defined as ALWAYS being 16 bits, and a long as
>>ALWAYS being 32 bits.....
>>So, on a 64-bit processor, what's an int?  For that matter, on machines larger
>>than 32 bits, what would short and long be?  
>According to our Cray programmers, on that 64-bit processor, a byte, a short,
>an int, and a long are all 64 bits.  kinda weird.  It must make something
>really fast....

I have heard that at least one Cray C compiler (is there more than one?)
converts all chars, ints, etc. to floats before performing math, and then
converts them back.  I hear that although the Cray is good at floats (esp.
many in a row), that the speed is terribly slow (about 5 x VAX 785).
These are all just things I heard, not necessarily based in fact.

Stefan Vorkoetter