Re: [PATCH] target/sparc: Fix gdbstub incorrectly handling registers f32-f62

On 2/13/25 11:03, Mikael Szreder wrote: Sorry. As you correctly pointed out there is no f33 register. I wrote f33, when I really meant f34. I believe the index of f32 is 64 and f34 is 65. This is confirmed when looking at the XML description of the registers in GDB:

Re: [PATCH] target/sparc: Fix gdbstub incorrectly handling registers f32-f62

Sorry. As you correctly pointed out there is no f33 register. I wrote f33, when I really meant f34. I believe the index of f32 is 64 and f34 is 65. This is confirmed when looking at the XML description of the registers in GDB:

Re: [PATCH] target/sparc: Fix gdbstub incorrectly handling registers f32-f62

On 2/3/25 06:50, Mikael Szreder wrote: The gdbstub implementation for the Sparc architecture would incorectly calculate the the floating point register offset. This would cause register pairs(eg f32,f33) to point to the same value. Fixes: 30038fd81808 ("target-sparc: Change fpr representation

Re: [PATCH] target/sparc: Fix gdbstub incorrectly handling registers f32-f62

Ping On February 3, 2025 3:50:56 PM GMT+01:00, Mikael Szreder wrote: >The gdbstub implementation for the Sparc architecture would incorectly > calculate the the floating point register offset. >This would cause register pairs(eg f32,f33) to point to the same value. > >Fixes: 30038fd81808 ("target

[PATCH] target/sparc: Fix gdbstub incorrectly handling registers f32-f62

The gdbstub implementation for the Sparc architecture would incorectly calculate the the floating point register offset. This would cause register pairs(eg f32,f33) to point to the same value. Fixes: 30038fd81808 ("target-sparc: Change fpr representation to doubles.") Signed-off-by: Mikael Szrede