Steve Underwood wrote:
Maik Heese wrote:
Dear All,
I think there is a bug in msp430-as,
which creates wrong binary code for:
*** @R0+, X(Rm)
MSPGCC does exactly the same thing with this code as the IAR assembler.
I think they should both report an error, rather than assemble the
instruction. However, the current behaviour is consistent with other tools.
mov @R0+,2(R4)
should assemble to:
b4 40 ?? ?? 02 00
but since the assembler has no way to fill in the question marks with
meaningful content I can't see any meaningful use of the instruction.
Regards,
Steve
Hello Steve,
I think your answer shows the right way to handle this instruction ...
the assembler should report an error.
Best regards,
Maik
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
