🚀 go-pugleaf

The file binutils-beta-1.94/binutils/m68k-pinsn.c has some problems with
exotic 68k opcodes.

1. It has no support for "P", "Y", "X", "W" and "Z" operand types (used by PMMU)

2. It searches the opcode table sequentially i.e. alphabetically, looking for
an opcode which matches the supplied hex opcode. This results in it finding
the floating point instructions Fxxxx before the pmmu ones Pxxxx and displaying
PMMU opcodes as "Fxxxx (cpid=0)" rather than as "unknown" which would be more
useful. Thus, even if you add support for Pxxx opcodes, they will not be found
unless they are placed out of order, before the Fxxx opcode descriptions in "m68k.h".
Is there more correct way of fixing this general problem than just rearranging 
"m68k.h"? It will occur anywhere where there are several alternative decodings
of an opcode.

Andrew Smith
Distributed Network Systems
SynOptics Communications Inc.