We don't currently have a well defined ISA string for compiling for a RVY base in integral pointer mode. Previous versions of the spec allowed rv64i_zyhybrid to enable all of the RVY base, but since the 0.9.8 move to custom3 space this is no longer possible (since we can't use that opcode space on an RVI base).
I think there are two options:
rv64i_xy (vendor/custom extension xy to enable RVY instructions). This is not great for a standard extension, but since we use vendor opcode space, it can't be zfoo.rv64y_zyfoo. I would imagine something like zyipm (RVY using integral pointer mode) could be a short RISC-Vy name?
We don't currently have a well defined ISA string for compiling for a RVY base in integral pointer mode. Previous versions of the spec allowed
rv64i_zyhybridto enable all of the RVY base, but since the 0.9.8 move to custom3 space this is no longer possible (since we can't use that opcode space on an RVI base).I think there are two options:
rv64i_xy(vendor/custom extensionxyto enable RVY instructions). This is not great for a standard extension, but since we use vendor opcode space, it can't bezfoo.rv64y_zyfoo. I would imagine something likezyipm(RVYusingintegralpointermode) could be a short RISC-Vy name?