From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2003-09-03 18:23:48
Hi!
On Wed, Sep 03, 2003 at 05:03:03PM +0200, Christian Krüger wrote:
> The first tests of da65 uncovered, that the 'da65'-cpu flag
> '--cpu 65C02' seems to have no effect.
> I get an output file where byte literals occur in the disassembled code
> (which is impossible for the 65C02, where all opcodes are defined).
For the 65C02 not all opcodes are defined. There are still undefined opcodes
which will be executed as a NOP by the CPU, but they're nevertheless
undefined.
> Beside this, I've got two (tiny) wishes:
> * in 65C02 mode it would be nice to have a cli-switch which enables
> commenting uncompatible 6502 code like this:
>
> ...
> rol a
> nop ; ! ($FB)
> sta $1234
> stz $5678 ; ! ($9C,$78,$56)
> ...
$FB will never get disassembled as NOP (the disassembler will use .byte $FB
instead). And I cannot see the real reason behind this switch. Maybe you can
tell me why you want this option.
> * it like to have the disass-output on stdout if no '-o' output
> file is specified. Actual, nothing happens if no output file
> is specified - IMHO quite confusing when using together with
> output redirection...
I've thought about this already, but none of the tools will currently produce
output on stdout, so I'm not sure if this behaviour would be confusing.
Thanks for the feedback!
Regards
Uz
--
Ullrich von Bassewitz uz_at_musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2003-09-03 18:24:04 CEST