Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!darekm
From: darekm@microsoft.UUCP (Darek MIHOCKA)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: The movep instruction & a strange display
Message-ID: <58845@microsoft.UUCP>
Date: 6 Nov 90 18:28:39 GMT
References: <1990Oct31.155603.4066@irscscm.UUCP> <1990Nov1.072136.24326@math.lsa.umich.edu>
Reply-To: darekm@microsoft.UUCP (Darek MIHOCKA)
Organization: Microsoft Corp., Redmond WA
Lines: 15

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
>with MADMAC and never had any trouble.) You can verify the correctness
>of the MADMAC object code just by looking at it in the Atari debugger.
>If it doesn't disassemble to what you're expecting, mebbe you're behind
>a rev or two on MADMAC?

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.

- Darek