From: Robert Riebisch <rr@bttr-software.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Dan-0411 / FIST bug
Date: Fri, 29 May 2009 23:20:30 +0200 [thread overview]
Message-ID: <4A20519E.1000501@bttr-software.de> (raw)
In-Reply-To: <5b31733c0905291344t4111d6ccv1fda02c67468397d@mail.gmail.com>
Filip Navara wrote:
> Maybe because nobody knows. I have only briefly looked into the code
OK. I thought, me wasn't worth an answer. ;-(
> and I believe it wasn't intentional and is just some side-effect of
> the implementation. In fact I believe more of the FPU flags are not
> reported correctly.
I wish QEMU having a bug tracking system, e.g., Bugzilla, Trac, or
Mantis, used by many / all people.
Robert Riebisch
--
BTTR Software
http://www.bttr-software.de/
prev parent reply other threads:[~2009-05-29 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 20:42 [Qemu-devel] Dan-0411 / FIST bug Robert Riebisch
2009-05-26 18:12 ` Robert Riebisch
2009-05-29 19:12 ` Robert Riebisch
2009-05-29 20:44 ` Filip Navara
2009-05-29 21:20 ` Robert Riebisch [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=4A20519E.1000501@bttr-software.de \
--to=rr@bttr-software.de \
--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).