From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1759264] Re: fpu/softfloat: round_to_int_and_pack refactor broke TriCore ftoi insns
Date: Mon, 16 Apr 2018 16:20:28 -0000 [thread overview]
Message-ID: <152389562935.19798.17137711647215533060.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 152215564388.18893.1601223531883570946.malonedeb@chaenomeles.canonical.com
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1759264
Title:
fpu/softfloat: round_to_int_and_pack refactor broke TriCore ftoi insns
Status in QEMU:
Fix Committed
Bug description:
After the refactor from ab52f973a504f8de0c5df64631ba4caea70a7d9e the
bahaviour of int32_to_float32() was altered.
helper_ftoi() in target/tricore/fpu_helper.c relied on
int32_to_float32 to raise the invalid flag if the input was NaN to
properly return 0. Likewise if the input is infinity.
The obvious fix for softfloat would be to raise this flag in round_to_int_and_pack(). However,
I'm not sure if this breaks other targets and I have no easy way to test it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1759264/+subscriptions
next prev parent reply other threads:[~2018-04-16 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 13:00 [Qemu-devel] [Bug 1759264] [NEW] fpu/softfloat: round_to_int_and_pack refactor broke TriCore ftoi insns Bastian Koppelmann
2018-04-10 20:07 ` [Qemu-devel] [Bug 1759264] " Alex Bennée
2018-04-11 9:23 ` Bastian Koppelmann
2018-04-11 11:01 ` Alex Bennée
2018-04-11 11:16 ` Bastian Koppelmann
2018-04-11 12:46 ` Bastian Koppelmann
2018-04-12 13:41 ` Alex Bennée
2018-04-13 14:09 ` Bastian Koppelmann
2018-04-16 16:20 ` Bastian Koppelmann [this message]
2018-04-26 5:10 ` Thomas Huth
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=152389562935.19798.17137711647215533060.launchpad@soybean.canonical.com \
--to=kbastian@mail.uni-paderborn.de \
--cc=1759264@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.