From: Andreas Schwab <schwab@linux-m68k.org>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] riscv: Add "Code:" to RISC-V splats
Date: Fri, 13 Jan 2023 16:49:30 +0100 [thread overview]
Message-ID: <87h6wutoxh.fsf@igel.home> (raw)
In-Reply-To: <20230113144552.138081-2-bjorn@kernel.org> ("Björn Töpel"'s message of "Fri, 13 Jan 2023 15:45:51 +0100")
On Jan 13 2023, Björn Töpel wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> Add "Code:" output to RISC-V splats. Mimic x86-64's byte-for-byte
> dumps.
RISC-V insns are organised in 16-bit parcels, it probably make sense to
present them that way.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] riscv: Add "Code:" to RISC-V splats
Date: Fri, 13 Jan 2023 16:49:30 +0100 [thread overview]
Message-ID: <87h6wutoxh.fsf@igel.home> (raw)
In-Reply-To: <20230113144552.138081-2-bjorn@kernel.org> ("Björn Töpel"'s message of "Fri, 13 Jan 2023 15:45:51 +0100")
On Jan 13 2023, Björn Töpel wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> Add "Code:" output to RISC-V splats. Mimic x86-64's byte-for-byte
> dumps.
RISC-V insns are organised in 16-bit parcels, it probably make sense to
present them that way.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-01-13 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:45 [PATCH 0/2] riscv: Add "Code:", and decodecode support Björn Töpel
2023-01-13 14:45 ` Björn Töpel
2023-01-13 14:45 ` [PATCH 1/2] riscv: Add "Code:" to RISC-V splats Björn Töpel
2023-01-13 14:45 ` Björn Töpel
2023-01-13 15:49 ` Andreas Schwab [this message]
2023-01-13 15:49 ` Andreas Schwab
2023-01-13 19:47 ` Björn Töpel
2023-01-13 19:47 ` Björn Töpel
2023-01-13 14:45 ` [PATCH 2/2] scripts/decodecode: Add support for RISC-V Björn Töpel
2023-01-13 14:45 ` Björn Töpel
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=87h6wutoxh.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.