home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!rpi!think.com!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!kitten.umdc.umu.se!cs.umu.se!dvljrt
- From: dvljrt@cs.umu.se (Joakim Rosqvist)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: OS 'Move/Draw' speed
- Message-ID: <C0LMr3.4q4@cs.umu.se>
- Date: 9 Jan 93 18:16:14 GMT
- References: <1993Jan8.050913.6571@gn.ecn.purdue.edu> <1ikc6nINNi3q@mercury.kingston.ac.uk> <1993Jan8.232345.9802@mpifr-bonn.mpg.de>
- Sender: news@cs.umu.se (News Administrator)
- Organization: Dep. of Info.Proc, Umea Univ., Sweden
- Lines: 12
-
- >Yep, writing single pixels is slow. Mainly because it needs to convert
- >an x,y coordinate to memory addresses and probably do some clipping.
- >The function call itself also adds some overhead.
-
- WritePixel is slow mainly because it uses the blitter.
- Why waste 6-8 chipram accesses to tell the blitter how to plot a pixel
- when the CPU can do it by itself with 2 accesses?
-
- '''
- /Joakim Rosqvist, $DR.HEX$) Email: dvljrt@cs.umu.se (o.o)
- ---------------------------------------------------------oOO--(_)--OOo-----
- Amiga coders do it 50 times per second.
-