public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson.chu@sifive.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v1] binutils/doc: Document the RISC-V -M options
Date: Fri, 25 Feb 2022 08:59:35 +0800	[thread overview]
Message-ID: <CAJYME4F+4MvGaW-OmXO+svQfDd6OFRrPBrRgnjswodRo_uU3Bg@mail.gmail.com> (raw)
In-Reply-To: <20220224183046.13473-1-palmer@rivosinc.com>

On Fri, Feb 25, 2022 at 2:32 AM Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> These have been around for quite a while now, but we forgot to actually
> document them.

LGTM, thanks!

Nelson

>         * doc/binutils.texi (-M): New section on RISC-V options.
>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
>  binutils/doc/binutils.texi | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/binutils/doc/binutils.texi b/binutils/doc/binutils.texi
> index 288974be386..bfb5a6199ca 100644
> --- a/binutils/doc/binutils.texi
> +++ b/binutils/doc/binutils.texi
> @@ -2693,6 +2693,19 @@ rather than names, for the selected types of registers.
>  You can list the available values of @var{ABI} and @var{ARCH} using
>  the @option{--help} option.
>
> +For RISC-V, this option controls how instructions are disassembled.  This
> +option can be provided multiple times, each time with a comma separated list
> +containing one or more of the following entries:
> +
> +@table @code
> +@item no-aliases
> +Avoid printing pseudo instruction mnemonics.
> +
> +@item numeric
> +Use numeric register names (ie, x1) instead of ABI register names (ie, ra) when
> +printing instructions.
> +@end table
> +
>  For VAX, you can specify function entry addresses with @option{-M
>  entry:0xf00ba}.  You can use this multiple times to properly
>  disassemble VAX binary files that don't contain symbol tables (like
> --
> 2.34.1
>

      reply	other threads:[~2022-02-25  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 18:30 Palmer Dabbelt
2022-02-25  0:59 ` Nelson Chu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJYME4F+4MvGaW-OmXO+svQfDd6OFRrPBrRgnjswodRo_uU3Bg@mail.gmail.com \
    --to=nelson.chu@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=palmer@rivosinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).