Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!aglew
From: aglew@ccvaxa.UUCP
Newsgroups: comp.arch
Subject: Re: register windows
Message-ID: <28200061@ccvaxa>
Date: Fri, 30-Oct-87 16:59:00 EST
Article-I.D.: ccvaxa.28200061
Posted: Fri Oct 30 16:59:00 1987
Date-Received: Mon, 2-Nov-87 05:20:06 EST
References: <201@PT.CS.CMU.EDU>
Lines: 20
Nf-ID: #R:PT.CS.CMU.EDU:201:ccvaxa:28200061:000:951
Nf-From: ccvaxa.UUCP!aglew    Oct 30 15:59:00 1987


..> Procedure call vs. interrupt frequency.

Something else to point out: globally optimizing compilers can do inline
expansion of much code, reducing procedure call overhead and frequency.
This cannot be done to interrupts.

Of course, there are a whole slew of tradeoffs here. Eg. reduced call
overhead vs. cache misses, if the function is called more than once.
Code size. Inlining militates against shared libraries.


Andy "Krazy" Glew. Gould CSD-Urbana.    USEnet:  ihnp4!uiucdcs!ccvaxa!aglew
1101 E. University, Urbana, IL 61801    ARPAnet: aglew@gswd-vms.arpa

I always felt that disclaimers were silly and affected, but there are people
who let themselves be affected by silly things, so: my opinions are my own,
and not the opinions of my employer, or any other organisation with which I am
affiliated. I indicate my employer only so that other people may account for
any possible bias I may have towards my employer's products or systems.