qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH] mips/gdbstub: Correct the handling of register #72 on writes
@ 2014-11-03 18:47 Maciej W. Rozycki
  2014-11-14  9:19 ` Leon Alrae
  0 siblings, 1 reply; 2+ messages in thread
From: Maciej W. Rozycki @ 2014-11-03 18:47 UTC (permalink / raw)
  To: qemu-devel; +Cc: Leon Alrae, Aurelien Jarno

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;

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Qemu-devel] [PATCH] mips/gdbstub: Correct the handling of register #72 on writes
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Leon Alrae @ 2014-11-14  9:19 UTC (permalink / raw)
  To: Maciej W. Rozycki, qemu-devel; +Cc: Aurelien Jarno

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>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-11-14  9:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).