From: Richard Henderson <richard.henderson@linaro.org>
To: Song Gao <gaosong@loongson.cn>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, f4bug@amsat.org,
alex.bennee@linaro.org, yangxiaojuan@loongson.cn
Subject: Re: [PATCH for-7.1 v2 1/5] target/loongarch: Fix GDB get the wrong pc
Date: Fri, 5 Aug 2022 08:03:11 -0700 [thread overview]
Message-ID: <69b9d443-1376-f9c9-96fc-8ab773a995d6@linaro.org> (raw)
In-Reply-To: <20220805033523.1416837-2-gaosong@loongson.cn>
On 8/4/22 20:35, Song Gao wrote:
> GDB LoongArch add a register orig_a0, see the base64.xml [1].
> We should add the orig_a0 to match the upstream GDB.
>
> [1]:https://github.com/bminor/binutils-gdb/blob/master/gdb/features/loongarch/base64.xml
>
> Signed-off-by: Song Gao<gaosong@loongson.cn>
> ---
> gdb-xml/loongarch-base64.xml | 1 +
> target/loongarch/cpu.c | 2 +-
> target/loongarch/gdbstub.c | 7 +++++--
> 3 files changed, 7 insertions(+), 3 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-08-05 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 3:35 [PATCH for-7.1 v2 0/5] Fix gdb bugs and update gdb-xml Song Gao
2022-08-05 3:35 ` [PATCH for-7.1 v2 1/5] target/loongarch: Fix GDB get the wrong pc Song Gao
2022-08-05 15:03 ` Richard Henderson [this message]
2022-08-05 3:35 ` [PATCH for-7.1 v2 2/5] target/loongarch: add gdb_arch_name() Song Gao
2022-08-05 3:35 ` [PATCH for-7.1 v2 3/5] target/loongarch: update loongarch-base64.xml Song Gao
2022-08-05 3:35 ` [PATCH for-7.1 v2 4/5] target/loongarch: Update loongarch-fpu.xml Song Gao
2022-08-05 15:05 ` Richard Henderson
2022-08-05 3:35 ` [PATCH for-7.1 v2 5/5] target/loongarch: Update gdb_set_fpu() and gdb_get_fpu() Song Gao
2022-08-05 15:14 ` Richard Henderson
2022-08-05 11:44 ` [PATCH for-7.1 v2 0/5] Fix gdb bugs and update gdb-xml Alex Bennée
2022-08-05 15:28 ` Richard Henderson
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=69b9d443-1376-f9c9-96fc-8ab773a995d6@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=gaosong@loongson.cn \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=yangxiaojuan@loongson.cn \
/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 NNTP newsgroup(s).