From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5123] Fix y register loads and stores
Date: Mon, 1 Sep 2008 17:39:40 -0400 (EDT) [thread overview]
Message-ID: <20080901173717.J84348@stanley.csl.cornell.edu> (raw)
In-Reply-To: <E1KaFBS-0003DQ-SJ@cvs.savannah.gnu.org>
On Mon, 1 Sep 2008, Blue Swirl wrote:
> Revision: 5123
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5123
> Author: blueswir1
> Date: 2008-09-01 19:35:29 +0000 (Mon, 01 Sep 2008)
My sample test case still fails (both on x86_64 and x86) even with this
patch.
I think something is still odd with the 64-bit multiply code (the rest of
the tcg instructions seem to work fine).
I'll investigate further.
Vince
next prev parent reply other threads:[~2008-09-01 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 19:35 [Qemu-devel] [5123] Fix y register loads and stores Blue Swirl
2008-09-01 21:39 ` Vince Weaver [this message]
2008-09-01 22:28 ` Vince Weaver
2008-09-01 23:05 ` Vince Weaver
2008-09-02 16:55 ` Blue Swirl
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=20080901173717.J84348@stanley.csl.cornell.edu \
--to=vince@csl.cornell.edu \
--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).