Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site gitpyr.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!houxm!whuxlm!akgua!gatech!gitpyr!robert
From: robert@gitpyr.UUCP (Robert Viduya)
Newsgroups: net.lang.c
Subject: Re: Potential optimisation?
Message-ID: <65@gitpyr.UUCP>
Date: Fri, 25-Jan-85 06:32:58 EST
Article-I.D.: gitpyr.65
Posted: Fri Jan 25 06:32:58 1985
Date-Received: Sun, 27-Jan-85 07:27:24 EST
References: <763@sjuvax.UUCP> <4305@ucbvax.ARPA> <1718@pucc-h>
Distribution: net
Organization: Georgia Tech, Atlanta
Lines: 23

> 2)  In a UNIX C compiler (to the best of my knowledge) two assembly
> procedures CSV and CRET are used to save and restore the registers in
> the *called* procedure.  I fail to see why this is desirable.  The
> *calling* procedure has full knowledge of which registers are being
> used and can save them itself.  This may not result in savings, but I
> don't see where it can result in a performance degradation.
> 

Then there's the Pyramid 90x machines where the registers (at least 32 of
them) are 'saved' (not really 'saved', more like 'pushed down') by the
machine itself without the need of special assembly procedures.  But that
topic was discussed a few months ago.


				robert
-- 
Robert Viduya
    Office of Computing Services
    Georgia Institute of Technology, Atlanta GA 30332
    Phone:  (404) 894-4669

...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp}!gatech!gitpyr!robert
...!{rlgvax,sb1,uf-cgrl,unmvax,ut-sally}!gatech!gitpyr!robert