Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!linac!unixhub!shelby!rutgers!mcdchg!heiby
From: heiby@mcdchg.chg.mcd.mot.com (Ron Heiby)
Newsgroups: comp.sys.m68k
Subject: Re: 68040 status
Message-ID: <56437@mcdchg.chg.mcd.mot.com>
Date: 14 Feb 91 21:20:16 GMT
References: <38696@cup.portal.com> <55919@mcdchg.chg.mcd.mot.com> <61711@masscomp.westford.ccur.com>
Organization: Motorola Computer Group, Schaumburg, IL
Lines: 16

joeo@sharp..westford.ccur.com (Joe Orost) writes:
>   Other than aligning the stack on a 16-byte boundary, and aligning all
>   external data modules on a similar boundary, how does a compiler take
>   advantage of the MOVE16 instruction?

Er, um, by generating object code for it?  Remember that the MOVE16
instruction did not exist before the MC68040.  So, compilers that
generate code for 68020 and 68030 processors will not be generating
MOVE16 instructions.  If they did, the executing code would be
trapping on an illegal instruction.  Now that the MC68040 exists, it
implements the MOVE16 instruction, so compilers can "take advantage of
the" new "MOVE16 instruction" by generating object code that uses it
to move blocks of memory around.
-- 
Ron Heiby, heiby@chg.mcd.mot.com	Moderator: comp.newprod
"Wrong is wrong, even when it helps you." Popeye