Xref: utzoo comp.lang.c:14509 comp.lang.misc:2274
Path: utzoo!utgpu!watmath!clyde!att!rutgers!gatech!mcnc!decvax!decwrl!sun!plx!evan
From: evan@plx.UUCP (Evan Bigall)
Newsgroups: comp.lang.c,comp.lang.misc
Subject: Re: Assembly or ....
Message-ID: <1487@plx.UUCP>
Date: 3 Dec 88 01:19:02 GMT
References: <1388@aucs.UUCP> <729@convex.UUCP> <1961@crete.cs.glasgow.ac.uk> <1988Nov29.181235.23628@utzoo.uucp> <960@vsi.COM>
Reply-To: evan@plx.UUCP (Evan Bigall)
Organization: Plexus Computers; San Jose, CA
Lines: 19

In article <960@vsi.COM> friedl@vsi.COM (Stephen J. Friedl) writes:
>In article <1988Nov29.181235.23628@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
>> Alas, if you buy your newer faster CPUs from Motorola or Intel, they can't
>> tell you how many cycles each instruction takes!
>
>Why is this?  When I was hacking on the VAX, nobody could ever
>tell me how long anything took, and empirical measurements were
>pretty tedious.  Is it laziness on the vendor's part or are there
>
>    Steve

I am not sure if this is their reason, but I used to work at a place where
people would hack the micro code at night.  You would come in the next day
and everything would take different amounts of time.  Made it very difficult
to document our progress on an optimizing compiler.

Evan
-----
{backbone}!sun!plx!evan