From: Jan Beulich <jbeulich@suse.com>
To: Branislav Brzak <Branislav.Brzak@Syrmia.com>
Cc: Dragoslav Sicarov <Dragoslav.Sicarov@Syrmia.com>,
Djordje Todorovic <Djordje.Todorovic@syrmia.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 0/1] riscv: Ensure LE instruction fetching
Date: Tue, 20 Jun 2023 13:44:46 +0200 [thread overview]
Message-ID: <32850550-cb52-039e-73ef-77227f425f3a@suse.com> (raw)
In-Reply-To: <AM6PR03MB49848E63E54AAB7B7C0D80E4985CA@AM6PR03MB4984.eurprd03.prod.outlook.com>
On 20.06.2023 13:43, Branislav Brzak wrote:
> Currently riscv gdb code looks at arch byte order
> when fetching instructions. This works when the
> target is LE, but on BE arch it will byte swap the
> instruction, while the riscv spec defines all
> instructions are LE encoded regardless of
> system memory endianess.
>
> Branislav Brzak (1):
> gdb/riscv: Ensure LE instruction fetching
>
> gdb/riscv-tdep.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Looks like you meant to send this to gdb-patches@sourceware.org?
Jan
next prev parent reply other threads:[~2023-06-20 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:43 Branislav Brzak
2023-06-20 11:44 ` Jan Beulich [this message]
2023-06-20 11:46 ` Branislav Brzak
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=32850550-cb52-039e-73ef-77227f425f3a@suse.com \
--to=jbeulich@suse.com \
--cc=Branislav.Brzak@Syrmia.com \
--cc=Djordje.Todorovic@syrmia.com \
--cc=Dragoslav.Sicarov@Syrmia.com \
--cc=binutils@sourceware.org \
/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).