RISC-V: Should the return value of print_insn_riscv() keep align with other platforms when read_memory_func() returns a non-zero value?

["Xiaolin Zheng" <yunyao.zxl@alibaba-inc.com>]

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

Hi, Binutils developers on the RISC-V backend:
Hope this is the right place to send one email to the Binutils mailing list. We have met a small issue [1] in OpenJDK when using the `disassembler()` API in `dis-asm.h` to disassemble. In the RISC-V backend of Binutils, if `read_memory_func` returns a `status`, a non-zero value, after calling `memory_error_func` we will use the `status` variable as the final return value [2], which is different from other platforms that use a `-1` as return value [3] [4] [5] [6]. Although we could have some workaround for this on our side, the question is, should the behavior keep the same as on other platforms?
Best Regards,
Xiaolin
[1] https://github.com/openjdk/jdk/pull/12551 <https://github.com/openjdk/jdk/pull/12551 >
[2] https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/riscv-dis.c#L940 <https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/riscv-dis.c#L940 >
[3] https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/aarch64-dis.c#L3792 <https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/aarch64-dis.c#L3792 >
[4] https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/ppc-dis.c#L872 <https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/ppc-dis.c#L872 >
[5] https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/s390-dis.c#L305 <https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/s390-dis.c#L305 >
[6] https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/i386-dis.c#L9466 <https://github.com/bminor/binutils-gdb/blob/binutils-2_38-branch/opcodes/i386-dis.c#L9466 >