Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!decwrl!shelby!polya!rokicki
From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.sys.amiga.tech
Subject: Re: ExecBase
Message-ID: <9641@polya.Stanford.EDU>
Date: 1 Jun 89 17:40:18 GMT
References: <8905242209.AA20811@postgres.Berkeley.EDU> <44325@vax1.tcd.ie>
Sender: Tomas G. Rokicki <rokicki@polya.Stanford.EDU>
Organization: Stanford University
Lines: 18

In article <44325@vax1.tcd.ie>, rwallace@vax1.tcd.ie writes:
> In article <8905242209.AA20811@postgres.Berkeley.EDU>, dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
> > 	I strongly suggest though that people who write programs or
> > assembly routines NOT always get execbase from location 4.  The reason is
> > simply that from what I can tell location 4 is in CHIP memory and thus
> > subject to fetch delays when one is in a high bandwidth video mode.

> You WHAT? How long is one instruction going to take no matter how high
> bandwidth a video mode you're using? If you're accessing ExecBase at all it
> means you're calling a ROM routine and those are so bloody inefficient the

If you are using one of those video modes that take up `all' bandwidth
(such as many under the new ECS, or hires four-bit plane) that *one*
instruction can easily take an entire scan-line, or 63us.  Most library
routines (such as exec) are not as inefficient as this.

Listen to Matt; he knows whereof he speaks of.
Wherefor dost thou question him?