Path: utzoo!attcan!uunet!munnari.oz.au!uokmax!apple!mips!zaphod.mps.ohio-state.edu!usc!ucsd!nosc!marlin!aburto
From: aburto@marlin.NOSC.MIL (Alfred A. Aburto)
Newsgroups: comp.sys.m68k
Subject: Re: Code too Big to ROM - where do we optimize
Message-ID: <1352@marlin.NOSC.MIL>
Date: 27 Mar 90 16:07:18 GMT
References: <5873@tekig5.PEN.TEK.COM>
Reply-To: aburto@marlin.nosc.mil.UUCP (Alfred A. Aburto)
Distribution: comp.sys.m68k
Organization: Naval Ocean Systems Center, San Diego
Lines: 23

In article <5873@tekig5.PEN.TEK.COM> barbaras@tekig5.PEN.TEK.COM 
(Barbara Ann Siefken) writes:
>Our code is too big to ROM.  Are there some assembly language
>statements or processes that are known to take less space if
>done another way?  Is that simplifying the question too much.
>
>	barbara Siefken
>	barbaras@tekig5


------      

Another useful code sequence is to replace CMP and BRANCH loops with
a DBF  --- this will save a bit of code and make the loop more efficient.
The loop range is only word size though --- I was hoping Motorola would
extend the range in the 68040, but alas they didn't ...

The book by Steve Williams; '68030 Assembly Language Reference',         
Addison-Wesley, 1989 discusses some code optimizations that you might
find useful .....
 
Al Aburto
aburto@marlin.nosc.mil