diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1838475')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1838475 | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1838475 b/results/classifier/zero-shot/108/other/1838475 new file mode 100644 index 000000000..57e59301c --- /dev/null +++ b/results/classifier/zero-shot/108/other/1838475 @@ -0,0 +1,50 @@ +semantic: 0.780 +device: 0.738 +socket: 0.693 +performance: 0.686 +network: 0.620 +vnc: 0.608 +permissions: 0.603 +other: 0.602 +debug: 0.567 +files: 0.544 +PID: 0.543 +graphic: 0.542 +boot: 0.517 +KVM: 0.343 + +qemu-system-arm exits when cortex-m4 floating point used and irq occurs + +qemu-system-arm exits with + +"...Secure UsageFault with CFSR.NOCP because NSACR.CP10 prevents stacking FP regs +...taking pending nonsecure exception 3 +Taking exception 7 [Breakpoint] +qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)" + +when emulating Cortex-m4, executing at least 1 floating point instruction, and then an irq (e.g. sys tick) occurring. + +CPACR.CP10 and CPACR.CP11 are set to 0x3 respectively prior to executing the fp instructions. + +NOTE: NSACR does not appear to be a cortex m4 register. + +Attached is a simplified elf to repro the issue. + +The qemu command line is: "qemu-system-arm --gdb tcp::1234 -cpu cortex-m4 -machine lm3s6965evb -nographic -semihosting-config enable=on,target=native -kernel QemuExitWhenUsingFPAndIRQOccurs.elf -d int" + + + +I think this patch should fix this bug: + +https://<email address hidden>/ + + +I confirm that this fixes the issue above. + +Thank you for your help! It is much appreciated. + +Now fixed in git master; will be in the imminent 4.1 release. + + +https://git.qemu.org/?p=qemu.git;a=commitdiff;h=02ac2f7f613b47f6a5b3 + |