🚀 go-pugleaf

In article <87@estinc.UUCP> fnf@estinc.UUCP (Fred Fish) writes:
>In article <8979@polya.Stanford.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>>
   The subject is optimizing 68000 branch instructions for forward branches.

   Tom explains a possible technique.

   Fred suggests assuming short branches then converting to long as needed
since once they are converted to long they will not need to be checked
again.


   I'm afraid that this falls into the pick your poison catagory.  If you
assume all branches to be long, once you start going back through the
code to shorten the branches, once they have been shortened they need
not be looked at again.  They will never fall back into the domain of
long branches (i.e. we only shrinking the code.)  It's the same thing,
only backwards.

   Assuming long first has at least one advantage:  You need not run
the optimizer if you don't want to take the time (probably minimal, but
at least you have a choice.) 



|    // GOATS - Gladly Offering All Their Support  Dave Kinzer (602)897-3085|
|   //  >> In Hell you need 4Mb to Multitask!  <<  uunet!mcdphx!teroach!dbk |
| \X/   #define policy_maker(name) (name->salary > 3 * dave.salary)         |