From: Kentaro Kawakami <1863247@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1863247] [NEW] AArch64 EXT instruction for V register does not clear MSB side bits
Date: Fri, 14 Feb 2020 13:06:50 -0000 [thread overview]
Message-ID: <158168561076.14835.7019812774701035317.malonedeb@soybean.canonical.com> (raw)
Public bug reported:
On AArch64 CPU with SVE register, there seems to be a bug in the
operation when executing EXT instruction to V registers. Bits above the
128 bits of the SVE register must be cleared to 0, but qemu-aarch64
seems to hold the value.
Example
ext v0.16b, v1.16b v2.16b, 8
After executing above instruction, (N-1) to 128 bits of z0 register must
be 0, where N is SVE register width.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1863247
Title:
AArch64 EXT instruction for V register does not clear MSB side bits
Status in QEMU:
New
Bug description:
On AArch64 CPU with SVE register, there seems to be a bug in the
operation when executing EXT instruction to V registers. Bits above
the 128 bits of the SVE register must be cleared to 0, but qemu-
aarch64 seems to hold the value.
Example
ext v0.16b, v1.16b v2.16b, 8
After executing above instruction, (N-1) to 128 bits of z0 register
must be 0, where N is SVE register width.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1863247/+subscriptions
next reply other threads:[~2020-02-14 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 13:06 Kentaro Kawakami [this message]
2020-02-14 17:51 ` [Bug 1863247] Re: AArch64 EXT instruction for V register does not clear MSB side bits Richard Henderson
2020-03-10 9:04 ` Laurent Vivier
2020-03-25 14:29 ` Kentaro Kawakami
2020-03-25 14:55 ` Richard Henderson
2020-04-30 13:29 ` Laurent Vivier
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=158168561076.14835.7019812774701035317.malonedeb@soybean.canonical.com \
--to=1863247@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).