home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.m68k
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!rpi!usenet.coe.montana.edu!news.u.washington.edu!stein.u.washington.edu!mpark
- From: mpark@stein.u.washington.edu (Michael Park)
- Subject: Re: 68000 code question and optimalisation
- Message-ID: <1992Nov24.013053.26137@u.washington.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington, Seattle
- References: <1992Nov23.104011.9355@philce.ce.philips.nl>
- Date: Tue, 24 Nov 1992 01:30:53 GMT
- Lines: 16
-
- In article <1992Nov23.104011.9355@philce.ce.philips.nl> meulenbr@ce.philips.nl (Frans Meulenbroeks) writes:
- ...
- >Also does anyone have suggestions on how to optimize 68000 code.
- >(eg. instructions or instruction patterns that can be replace by other
- >more efficient ones)? A pointer to a good book/article on this topic is
- >also welcome. I want to optimize for space without losing too much
- >speed.
-
- A fun article to read is "Superoptimizer -- A Look at the Smallest Program"
- by Henry Massalin. It's actually for '020, but probably still useful.
-
- It's from some ACM thing (I got a photocopy from a friend); at the bottom
- of the page it says "(c) 1987 ACM 0-89791-238-1/87/1000-0122 $00.75"
- if that helps.
-
- --m
-