PPC binutils opcodes

[Luke Kenneth Casson Leighton]

(please do reply cc as i am subscribed digest, thank you for understanding)

On Wed, May 11, 2022 at 10:24 AM Dmitry Selyutin <ghostmansd@gmail.com> wrote:

> The trivial and obvious solution to increase the size of the operand
> index[3] can be done,

direct to the diff may be helpful:
https://git.libre-soc.org/?p=binutils-gdb.git;a=commitdiff;h=b4a728e26f4c364f1a4d365c3c4e5e2441f70a5e;hp=bdb7c7d203c3f155e5e2834b7781c0fd173d5e6c

another helpful resource: a machine-readable version of the fields, taken
from the v3.0B specification, verbatim:

https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=openpower/isatables/fields.text;h=eb962688ca674db58b65100a159c1b20cfbbb886;hb=e4142b9e970ae21639ed5a8884d193f57ffc463a#l294

aside from the Draft SVP64 fields i am only seeing appx 130 v3.0B fields.
if not for pseudo-fields there should have been plenty of room.

with the OpenPOWER Foundation inviting others to add Custom Extensions
and also the OPF ISA WG being set up and welcoming contributions to the
Power ISA it would be anomalous that binutils has this built-in limit on the
number of potential opcode fields.  we happen to be the first to encounter
that limit.
https://openpowerfoundation.org/groups/isa/

l.