[PATCH 1/1] doc/riscv: Add description of disassembler options

[Jan Beulich]

On 26.03.2025 03:33, Nelson Chu wrote:
> This is okay from my side, thanks.  Btw, the privileged spec 1.9.1 support
> was removed since binutils 2.43, so the option of objdump should also
> remove it.  The linker only recognizes it and then reports a warning that
> it may conflict with other spec versions.

It's imo okay to go in as-is. I'd like to note though that it looks as if
originally the architecture specific sections were sorted alphabetically
(and hence the addition might better go between PPC and VAX). That sorting
was partly broken by ix86 having got renamed to x86 (but left in place),
by aarch64 having got inserted after Arm, and by MIPS having ended up
between PPC and VAX.

Jan

> On Wed, Mar 26, 2025 at 3:50 AM Marek Pikuła <m.pikula@partner.samsung.com>
> wrote:
> 
>> Up to this point, no mention of RISC-V-specific disassembler options
>> wasn't mentioned in binutils documentation. This patch includes
>> description for all of the currently supported options.
>>
>> Signed-off-by: Marek Pikuła <m.pikula@partner.samsung.com>
>> ---
>>  binutils/doc/binutils.texi | 17 +++++++++++++++++
>>  1 file changed, 17 insertions(+)
>>
>> diff --git a/binutils/doc/binutils.texi b/binutils/doc/binutils.texi
>> index 73848e3b390..f8c5bd927fb 100644
>> --- a/binutils/doc/binutils.texi
>> +++ b/binutils/doc/binutils.texi
>> @@ -2764,6 +2764,23 @@ ROM dumps).  In these cases, the function entry
>> mask would otherwise
>>  be decoded as VAX instructions, which would probably lead the rest
>>  of the function being wrongly disassembled.
>>
>> +For RISC-V, the following options are supported:
>> +
>> +@table @code
>> +@item numeric
>> +Print numeric register names, rather than ABI names (e.g., print @code{x2}
>> +instead of @code{sp}).
>> +
>> +@item no-aliases
>> +Disassemble only into canonical instructions. For example, compressed
>> +instructions will be represented as such (@code{addi sp,sp,-128} will be
>> +@code{c.addi16sp sp,-128}).
>> +
>> +@item priv-spec=@var{SPEC}
>> +Print the CSR according to the chosen privilege spec version (e.g.,
>> +@code{1.9.1}, @code{1.10}, @code{1.11}, @code{1.12}).
>> +@end table
>> +
>>  @item -p
>>  @itemx --private-headers
>>  Print information that is specific to the object file format.  The exact
>> --
>> 2.49.0
>>
>>
>