Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.arch,net.micro.68k
Subject: Re: M680*0 "small model"
Message-ID: <2312@sun.uucp>
Date: Sun, 16-Jun-85 23:01:57 EDT
Article-I.D.: sun.2312
Posted: Sun Jun 16 23:01:57 1985
Date-Received: Wed, 19-Jun-85 02:00:31 EDT
References: <167@mot.UUCP> <1069@peora.UUCP> <1071@peora.UUCP>
Organization: Sun Microsystems, Inc.
Lines: 20
Xref: watmath net.arch:1415 net.micro.68k:930

> > It sounds to me like what the 68000 needs is an optimizing assembler.
> > On Perkin-Elmer 3200 series computers there are several addressing
> > modes, using from 2 to 6 bytes per instruction. The assembler
> > automatically figures the best addressing mode and generates the
> > appropiate object code.

> Actually the better 8086 assemblers do this.

Heck, guys, the UNIX PDP-11 assembler does this for branch instructions.  So
does the UNIX VAX-11 assembler and the MIT and AT&T 68000 assemblers.

> > It seems to me that such a optimizer could be used as a post-processor
> > for the compiler allowing all languages to use this technique. You
> > should also have the option of running without squeeze to save compile
> > time during debug.

Since PCC-derived C compilers and "f77"-derived FORTRAN 77 compilers
generate assembly code instead of object code, they all use this technique.

	Guy Harris