home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!darwin.sura.net!convex!linac!att!bu.edu!dartvax!Joe.Francis
- From: Joe.Francis@dartmouth.edu (Joe Francis)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: Optimizing 680x0 code
- Message-ID: <1992Aug26.175046.15921@dartvax.dartmouth.edu>
- Date: 26 Aug 92 17:50:46 GMT
- References: <1992Aug25.143954.5875@hobbes.kzoo.edu>
- Sender: news@dartvax.dartmouth.edu (The News Manager)
- Organization: Dartmouth College, Hanover, NH
- Lines: 19
- X-Posted-From: InterNews1.0d56@newshost.dartmouth.edu
-
- In article <1992Aug25.143954.5875@hobbes.kzoo.edu>
- k044477@hobbes.kzoo.edu (Jamie R. McCarthy) writes:
-
- > I am in the lucky position of knowing exactly where my program needs to
- > be faster. The time-consuming bits are smallish, fairly straightforward
- > routines that extract data from one of a variety of compression
- > techniques. Lots of shuffling bits within words and so forth.
-
- Gee, sounds like a TIFF viewer!
-
- > It'd be way cool if some assembler hacker were willing to
- > take a look at the code and try to make it faster. Would anyone with
- > time on their hands (yeah right) be willing to partake of a little
- > intellectual exercise?...
-
- I doubt it. But I can opint you to a good article that may allow you
- to achieve good results on your own. One of the recent MacTutors had a
- good article on 680x0 assembly optimization. Check it out. I'll be
- using it myself soon.
-