From: Hansni Bu <1924669@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1924669] Re: VFP code cannot see CPACR write in the same TB
Date: Wed, 21 Apr 2021 08:07:36 -0000 [thread overview]
Message-ID: <161899245704.10328.7546492827536683605.malone@wampee.canonical.com> (raw)
In-Reply-To: 161854448336.19133.14178473340326539208.malonedeb@wampee.canonical.com
Sorry, it's because a "ISB" is missing after CPACR is changed. Not bug
of qemu.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1924669
Title:
VFP code cannot see CPACR write in the same TB
Status in QEMU:
Invalid
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1924669/+subscriptions
prev parent reply other threads:[~2021-04-21 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 3:41 [Bug 1924669] [NEW] VFP code cannot see CPACR write in the same TB Hansni Bu
2021-04-21 8:07 ` Hansni Bu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161899245704.10328.7546492827536683605.malone@wampee.canonical.com \
--to=1924669@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).