From: Leon Alrae <leon.alrae@imgtec.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>, qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] mips/gdbstub: Correct the handling of register #72 on writes
Date: Fri, 14 Nov 2014 09:19:01 +0000 [thread overview]
Message-ID: <5465C905.8050303@imgtec.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1411031836290.2881@tp.orcam.me.uk>
On 03/11/2014 18:47, Maciej W. Rozycki wrote:
> Fix an off-by-one error in `mips_cpu_gdb_write_register' for register
> #72 that is handled further down in that function rather than here,
> matching how `mips_cpu_gdb_read_register' handles it. This register
> slot is a fake anyway, there's nothing in hardware that corresponds to
> it.
>
> Signed-off-by: Maciej W. Rozycki <macro@codesourcery.com>
> ---
> I have a further change down the queue to clean up
> `mips_cpu_gdb_read_register' and `mips_cpu_gdb_write_register' and make
> them more consistent with respect to each other as far as the handling
> of FP registers is concerned. For now please apply this obvious change.
> Thanks.
>
> Maciej
>
> qemu-mips-fpreg72.diff
> Index: qemu-git-trunk/target-mips/gdbstub.c
> ===================================================================
> --- qemu-git-trunk.orig/target-mips/gdbstub.c 2013-07-29 11:23:07.048742983 +0100
> +++ qemu-git-trunk/target-mips/gdbstub.c 2014-10-27 04:17:19.159003270 +0000
> @@ -97,7 +97,7 @@ int mips_cpu_gdb_write_register(CPUState
> return sizeof(target_ulong);
> }
> if (env->CP0_Config1 & (1 << CP0C1_FP)
> - && n >= 38 && n < 73) {
> + && n >= 38 && n < 72) {
> if (n < 70) {
> if (env->CP0_Status & (1 << CP0St_FR)) {
> env->active_fpu.fpr[n - 38].d = tmp;
>
Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>
prev parent reply other threads:[~2014-11-14 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 18:47 [Qemu-devel] [PATCH] mips/gdbstub: Correct the handling of register #72 on writes Maciej W. Rozycki
2014-11-14 9:19 ` Leon Alrae [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=5465C905.8050303@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=macro@codesourcery.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).