qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc smul problem
Date: Mon, 1 Sep 2008 19:49:10 +0300	[thread overview]
Message-ID: <f43fc5580809010949p4d445fd2q240606d1f2a7059e@mail.gmail.com> (raw)
In-Reply-To: <20080901121035.R83237@stanley.csl.cornell.edu>

On 9/1/08, Vince Weaver <vince@csl.cornell.edu> wrote:
> Hello!
>
>  I've been stuck on this all weekend, as I can't find where the actual
> problem is. I might be completely missing it, but I've tried a lot of things
> and can't make it work.
>
>  On SPARC, the "smul" instruction multiplies two numbers, puts the result in
> the result register but also puts the top 32-bits of the 64-bit result into
> the "Y" register.
>
>  As the attached code shows, the value of "Y" is wrong.  Somehow after the
> multiply, the top 32 bits of the product rae all zeros.  I've played around
> with the code generated by translate.c, and it looks like the shift and
> other instructions all work properly, but the 64-bit multiply the result is
> somehow being truncated.  But I've looked at the generated code (on x86_64)
> and it looks like it is doing the right thing.
>
>  So anyway, I'll have to take a look at this again later, but in case anyone
> else wants to look at it in case I am missing anything obvious.

At least the store and load do not match:
 ---- 0x10084
 mov_i64 tmp16,g1
 mov_i64 tmp17,g4
 mul_i64 tmp17,tmp16,tmp17
 movi_i64 tmp18,$0x20
 shr_i64 tmp16,tmp17,tmp18
 st_i32 tmp16,env,$0x58
^^^^^
 mov_i64 loc3,tmp17
 mov_i64 g2,loc3

 ---- 0x10088
 ld_i64 tmp0,env,$0x58
^^^^^
mov_i64 g3,tmp0

  reply	other threads:[~2008-09-01 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 16:14 [Qemu-devel] sparc smul problem Vince Weaver
2008-09-01 16:49 ` Blue Swirl [this message]
2008-09-01 17:20 ` Blue Swirl
2008-09-01 19:05 ` Blue Swirl
2008-09-01 23:11   ` Aurelien Jarno
2008-09-02 16:58   ` 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=f43fc5580809010949p4d445fd2q240606d1f2a7059e@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --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).