diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1924669')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1924669 | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1924669 b/results/classifier/zero-shot/108/other/1924669 new file mode 100644 index 000000000..499a8aeab --- /dev/null +++ b/results/classifier/zero-shot/108/other/1924669 @@ -0,0 +1,30 @@ +graphic: 0.830 +device: 0.568 +semantic: 0.542 +vnc: 0.489 +network: 0.455 +performance: 0.448 +other: 0.353 +PID: 0.266 +socket: 0.263 +permissions: 0.248 +debug: 0.236 +boot: 0.206 +KVM: 0.173 +files: 0.120 + +VFP code cannot see CPACR write in the same TB + +If FPU is enabled by writing to CPACR, and the code is in the same translation block as the following VFP code, qemu generates "v7M NOCP UsageFault". + +This can be reproduced with git HEAD (commit 8fe9f1f891eff4e37f82622b7480ee748bf4af74). + +The target binary is attached. The qemu command is: +qemu-system-arm -nographic -monitor null -serial null -semihosting -machine mps2-an505 -cpu cortex-m33 -kernel cpacr_vfp.elf -d in_asm,int,exec,cpu,cpu_reset,unimp,guest_errors,nochain -D log + +If the code is changed a little, so that they are not in the same block, VFP code can see the effect of CPACR, or -singlestep of qemu has the same result. + + + +Sorry, it's because a "ISB" is missing after CPACR is changed. Not bug of qemu. + |