From: Evan Nemerson <1883784@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1883784] [NEW] [ppc64le] qemu behavior differs from ppc64le hardware
Date: Tue, 16 Jun 2020 20:27:45 -0000 [thread overview]
Message-ID: <159233926606.29237.7012634601262116409.malonedeb@chaenomeles.canonical.com> (raw)
Public bug reported:
I have some code which passes my test suite on PPC64LE hardware when
compiled with GCC 10, but the saem binary fails with both qemu-ppc64le
4.2 (on Fedora 32) and qemu-ppc64le-static 5.0.0 (Debian testing).
I'm not getting any errors about illegal instructions or anything, like
that; the results are just silently different on qemu.
I've generated a reduced test case, which is attached along with the
binaries (both are the same code, one is just statically linked). They
should execute successufully on PPC64LE hardware, but on qemu they hit a
__builtin_abort (because the computed value doesn't match the expected
value).
Without being familiar with PPC assembly I'm not sure what else I can
do, but if there is anything please let me know.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: ppc64le
** Attachment added: "test case"
https://bugs.launchpad.net/bugs/1883784/+attachment/5384531/+files/mm_cvtpd_ps.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1883784
Title:
[ppc64le] qemu behavior differs from ppc64le hardware
Status in QEMU:
New
Bug description:
I have some code which passes my test suite on PPC64LE hardware when
compiled with GCC 10, but the saem binary fails with both qemu-ppc64le
4.2 (on Fedora 32) and qemu-ppc64le-static 5.0.0 (Debian testing).
I'm not getting any errors about illegal instructions or anything,
like that; the results are just silently different on qemu.
I've generated a reduced test case, which is attached along with the
binaries (both are the same code, one is just statically linked).
They should execute successufully on PPC64LE hardware, but on qemu
they hit a __builtin_abort (because the computed value doesn't match
the expected value).
Without being familiar with PPC assembly I'm not sure what else I can
do, but if there is anything please let me know.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1883784/+subscriptions
next reply other threads:[~2020-06-16 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 20:27 Evan Nemerson [this message]
2020-06-16 21:22 ` [Bug 1883784] Re: [ppc64le] qemu behavior differs from ppc64le hardware Alex Bennée
2020-06-17 8:19 ` Laurent Vivier
2020-06-17 11:53 ` Michael R. Crusoe
2021-05-07 2:50 ` Thomas Huth
2021-07-06 4:17 ` Launchpad Bug Tracker
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=159233926606.29237.7012634601262116409.malonedeb@chaenomeles.canonical.com \
--to=1883784@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).