All of lore.kernel.org
 help / color / mirror / Atom feed
From: claude vittoria <vittoric@wanadoo.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PPC] FPIMM macro and mtfsfi instruction
Date: Mon, 17 Dec 2007 15:52:56 +0100 (CET)	[thread overview]
Message-ID: <15604398.56931197903176591.JavaMail.www@wwinf1607> (raw)

Hi everybody,

I think that I get a wrong result with mtfsfi instruction.

I think to get a solution, see below.
Could you confirm my opinion ?

Thanks,
Claude

translate.c 
l344:EXTRACT_HELPER(crbD, 21, 5);
...
l375:EXTRACT_HELPER(FPIMM, 20, 4); <======FPIMM must be (FPIMM, 12, 4) or crbB >> 1 for mtfsfi; IMM is bits[16-19] of the instruction in PPC programming environnement 32bit (p8-135). IMM is not one bit before crbD.
...
l2049
/* mtfsfi */
GEN_HANDLER(mtfsfi, 0x3F, 0x06, 0x04, 0x006f0800, PPC_FLOAT)
{
    int bf, sh;

    if (unlikely(!ctx->fpu_enabled)) {
        GEN_EXCP_NO_FP(ctx);
        return;
    }
    bf = crbD(ctx->opcode) >> 2;                 <======================Ok bits[6-8]
    sh = 7 - bf;
    gen_optimize_fprf();
    gen_op_set_FT0(FPIMM(ctx->opcode) << (4 * sh)); <===================FPIMM is not correct, does not return the right value but bits [8-11]
    gen_reset_fpstatus();
    gen_op_store_fpscr(1 << sh);
    if (unlikely(Rc(ctx->opcode) != 0)) {
        gen_op_load_fpcc();
        gen_op_set_Rc0();
    }
    /* We can raise a differed exception */
    gen_op_float_check_status();
}

             reply	other threads:[~2007-12-17 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 14:52 claude vittoria [this message]
2007-12-17 17:32 ` [Qemu-devel] [PPC] FPIMM macro and mtfsfi instruction Jocelyn Mayer
  -- strict thread matches above, loose matches on Subject: below --
2007-12-18  8:49 claude vittoria

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=15604398.56931197903176591.JavaMail.www@wwinf1607 \
    --to=vittoric@wanadoo.fr \
    --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.