Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!ohlone!nelson
From: nelson@ohlone.UUCP
Newsgroups: comp.arch,comp.lang.c
Subject: Re: Tuning your libraries for your machine
Message-ID: <168@ohlone.UUCP>
Date: Mon, 6-Apr-87 05:26:37 EST
Article-I.D.: ohlone.168
Posted: Mon Apr  6 05:26:37 1987
Date-Received: Thu, 9-Apr-87 03:49:26 EST
References: <15292@amdcad.UUCP> <978@ames.UUCP> <15694@sun.uucp> <1530@husc6.UUCP> <1959@hoptoad.uucp>
Organization: Cray Research Inc., Livermore, CA
Lines: 17
Xref: utgpu comp.arch:799 comp.lang.c:1497
Summary: Cray's don't work like Vaxen

In article <1959@hoptoad.uucp>, gnu@hoptoad.uucp (John Gilmore) writes:
> It only becomes reasonable to tailor a system for a particular piece of
> hardware when there are only a small number of variants that run that
> architecture.
> [...]
> (Of course, the same applies to an "architecture" like C/Unix -- write
> code that's straightforward and doesn't do anything that really breaks
> anywhere.  Super optimizing your C source is kinda hard these days --
> are you *sure* it's better to code it this way on the Cray?  IBM?  DG?
> DEC?  8080?)

Right on!  Things like a[i++] = *++p; are totally lost on a Cray.
Unfortunately, the current Cray C compiler is none too great ... we're
working on it!
-----------------------
Bron Nelson     {ihnp4, lll-lcc}!ohlone!nelson
Not the opinions of Cray Research