[RFC] Add a second 'pinfo' member to mips_opcode to extend number of available bits

[Ian Lance Taylor]

Fred Fish <fnf@specifixinc.com> writes:

> (2) The mips opcode tables contain entries that look and taste like
> all the other entries, but are really there just to make some special
> cases of a general instruction more logical from a programmer point of
> view.  For example, 'nop' is just a special case of an 'sll'
> instruction; 'daddu', 'addu', and 'or' with a zero input operand can
> all be thought of as a 'move', etc.  For the purposes of this patch
> I've called these transformations 'aliases', as distinct from 'macros'
> which are handled differently.  Some programmers prefer to see the
> actual non-alias instruction in the disassembly output.  So I added a
> 'no-aliases' option for objdump's -M to use.  I.E.:

We need to document no-aliases somewhere, or nobody will ever find out
about it.  Where should we do this?

It should also go into binutils/NEWS.

Ian