Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!math.lsa.umich.edu!math.lsa.umich.edu!hyc
From: hyc@math.lsa.umich.edu (Howard Chu)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: The movep instruction & a strange display
Message-ID: <1990Nov6.220919.12166@math.lsa.umich.edu>
Date: 6 Nov 90 22:09:19 GMT
References: <1990Oct31.155603.4066@irscscm.UUCP> <1990Nov1.072136.24326@math.lsa.umich.edu> <58845@microsoft.UUCP>
Sender: usenet@math.lsa.umich.edu
Organization: University of Michigan Math Dept., Ann Arbor
Lines: 19

In article <58845@microsoft.UUCP> darekm@microsoft.UUCP (Darek MIHOCKA) writes:
>In article <1990Nov1.072136.24326@math.lsa.umich.edu> hyc@math.lsa.umich.edu (Howard Chu) writes:
>>I know that incorrect code is generated for movep by both the 2.0 and
>>3.0 MWC assemblers. (Different incorrect code, too!) However, I'm pretty
>>sure that MADMAC handles movep correctly. (I've used it a number of times

>The two versions of MadMac that I have both generate correct code for MOVEP.
>But all versions of Megamax C and Laser C generate incorrect code for MOVEP.
>(That's if youre using the inline assembler). The inline assembler also
>generates incorrect code for DC.B and DC.L and some branch instructions.

Mebbe this explains the phrase in my 68000 book: "the MOVEP instruction
is probably never generated by a compiler..." The compiler writers don't
care about it and then their code can't generate it. Yeehah.
--
  -- Howard Chu @ University of Michigan

Mac// - adv., q.v. MacToo, e.g.  McHave a McHappy McDay!
		McThanks, McYou MacToo!