aboutsummaryrefslogtreecommitdiff
path: root/scripts/render_block_graph.py
diff options
context:
space:
mode:
authorPeter Maydell <peter.maydell@linaro.org>2025-01-24 16:27:23 +0000
committerPeter Maydell <peter.maydell@linaro.org>2025-01-28 18:40:19 +0000
commit1edc3d43f20df0d04f8d00b906ba19fed37512a5 (patch)
tree2557cf100fb78ced824459d290c181056f616774 /scripts/render_block_graph.py
parentcb5f6ca8af0f1dd2f55008855e542ec33479e929 (diff)
downloadqemu-1edc3d43f20df0d04f8d00b906ba19fed37512a5.zip
qemu-1edc3d43f20df0d04f8d00b906ba19fed37512a5.tar.gz
qemu-1edc3d43f20df0d04f8d00b906ba19fed37512a5.tar.bz2
target/arm: arm_reset_sve_state() should set FPSR, not FPCR
The pseudocode ResetSVEState() does: FPSR = ZeroExtend(0x0800009f<31:0>, 64); but QEMU's arm_reset_sve_state() called vfp_set_fpcr() by accident. Before the advent of FEAT_AFP, this was only setting a collection of RES0 bits, which vfp_set_fpsr() would then ignore, so the only effect was that we didn't actually set the FPSR the way we are supposed to do. Once FEAT_AFP is implemented, setting the bottom bits of FPSR will change the floating point behaviour. Call vfp_set_fpsr(), as we ought to. (Note for stable backports: commit 7f2a01e7368f9 moved this function from sme_helper.c to helper.c, but it had the same bug before the move too.) Cc: qemu-stable@nongnu.org Fixes: f84734b87461 ("target/arm: Implement SMSTART, SMSTOP") Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Message-id: 20250124162836.2332150-4-peter.maydell@linaro.org
Diffstat (limited to 'scripts/render_block_graph.py')
0 files changed, 0 insertions, 0 deletions