Re: A92: Re: optimization

To: assembly-92@lists.ticalc.org
Subject: Re: A92: Re: optimization
From: Arno.Kizina@t-online.de (Arno Kizina)
Date: Sun, 30 Aug 1998 02:13:46 +0200
Delivered-To: assembly-92-outgoing@towerguard.unix.edu.sollentuna.se
References: <002801bdd370$62cc5c80$f8c5fea9@oemcomputer>
Reply-To: assembly-92@lists.ticalc.org


Aaron Hill schrieb:

> Here are a few tips for optimazations (PROJECT ALERT: Create a webpage with
> information for optimizing various types of code.)
>     * Stack "clean-up"... I've seen several choices for fixing the stack
> pointer after function calls.  The best I've seen is a simple "ADD.W ?,a7"
> where the ? is the byte offset.  I'm pretty sure that the MOVE's and PEA's
> are slower than the ADD (considering that the addressing mode ?(a7) used
> with fixing the stack pointer probably uses the ADD).
I'm pretty sure that you are wrong,lea #n(a7),a7 takes 8 cycles, addq #n,a7 
takes 8 cycles,too, but can only be used for additions lower than 9 and 
add(a).w(l) #n,a7 takes 12(w)/16(l) cycles to perform.	(taken from a file 
called takt_tab.s that was stored on my Atari 68k)	A.K. 

> p.s. (TO ALL) Watch the mailing list soon!!  I'll be making an announcement
> today
> ====
> Aaron Hill (Redmond, WA)
> E-mail: SeracOhw24@msn.com
> IRC Nick: SeracOhw (EF-Net)
>
>
>

References:

A92: Re: optimization

From: "Aaron Hill" <SeracOhw24@email.msn.com>

Prev: Re: A92: Memory layout of the 92plus
Next: A92: Paint Program
Index(es):
- Main
- Thread