From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Bug 1759264 <1759264@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1759264] Re: fpu/softfloat: round_to_int_and_pack refactor broke TriCore ftoi insns
Date: Wed, 11 Apr 2018 13:16:27 +0200 [thread overview]
Message-ID: <20fc82c8-85d5-7fdf-947d-0907d665161f@mail.uni-paderborn.de> (raw)
In-Reply-To: <87woxe3t2t.fsf@linaro.org>
On 04/11/2018 01:01 PM, Alex Bennée wrote:
>
> Bastian Koppelmann <kbastian@mail.uni-paderborn.de> writes:
>
>> On 04/10/2018 10:07 PM, Alex Bennée wrote:
>>> Yeah it looks like it was missed, the round_to_uint code does it.
>>>
>>> Do you have a test case I can verify?
>>>
>>
>> For the NaN input 0xffffffff the expected result for the flags is that
>> flag_invalid is raised.
>>
>> I can provide you with some TriCore asm, but it is a bit of pain to get
>> the gnu assembler to build, since the public version is a decade old.
>
> I'll trust you if you send me a static binary for this particular
> verification ;-)
>
> It would be nice to TriCore tests building in tests/tcg/ but I guess we
> need an up to date cross compile environment somewhere.
That is the problem. There is a gcc/binutils port done by some german
company. And it's not easy to get the source. The one they provide is
pretty old and needs some patching to get in building on modern
machines. Right now I'm trying to set up a test environment.
Cheers,
Bastian
next prev parent reply other threads:[~2018-04-11 11:16 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 [this message]
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
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=20fc82c8-85d5-7fdf-947d-0907d665161f@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=1759264@bugs.launchpad.net \
--cc=alex.bennee@linaro.org \
--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).