Plugin-based opcode table

Dmitry Selyutin ghostmansd@gmail.com
Mon May 23 13:06:17 GMT 2022


On Mon, May 23, 2022 at 3:59 PM Alan Modra <amodra@gmail.com> wrote:
> I don't see any need for the artificial boundaries you might get with
> a plugin, whatever that might look like.  ppc-opc.c already supports
> multiple incompatible powerpc cpu implementations, including ones that
> depart significantly from current powerpc ISA documentation.

Alan, please, correct me if I'm wrong: does it mean that we can just
stick to marking new instructions and facilities with a custom per-CPU
flag? For now I introduced the -mlibresoc CPU which enabled the
PPC_OPCODE_SVP64 flag, and marked some new instructions appropriately
with this flag. Would that be OK if we follow this approach?


More information about the Binutils mailing list