qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jun Koi" <junkoi2004@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] understanding how arpl is translated
Date: Tue, 13 May 2008 12:32:00 +0900	[thread overview]
Message-ID: <fdaac4d50805122032j4923a2fbs7fc5ab4aeabb30cc@mail.gmail.com> (raw)

Hi,

I am trying to understand how "arpl" insn (i386) is translated. In
translate.c we have:

.....
modrm = ldub_code(s->pc++);
reg = (modrm >> 3) & 7;
mod = (modrm >> 6) & 3;
rm = modrm & 7;
if (mod != 3) {
    gen_lea_modrm(s, modrm, &reg_addr, &offset_addr);
    gen_op_ld_T0_A0(ot + s->mem_index);      // (1)  ****
} else {
    gen_op_mov_TN_reg(ot, 0, rm);                   // (2)  ****
}
if (s->cc_op != CC_OP_DYNAMIC)
    gen_op_set_cc_op(s->cc_op);
gen_op_arpl();
s->cc_op = CC_OP_EFLAGS;
...

I can see that we decrypt 2 operands of arpl and then call
gen_op_arpl(). This function finally leads to execute op_arpl(), which
is defined as:

void OPPROTO op_arpl(void)
{
    if ((T0 & 3) < (T1 & 3)) {
        /* XXX: emulate bug or 0xff3f0000 oring as in bochs ? */
        T0 = (T0 & ~3) | (T1 & 3);
        T1 = CC_Z;
   } else {
        T1 = 0;
    }
    FORCE_RET();
}

Obviously op_arpl() relies on T0 and T1 have the value of the 1st and
2nd operands of the above "arpl" insn. However, I can only see that we
copy the 1st operand into T0 at (1) or (2) in the first snippet, but I
never see when we copy 2nd operand into T1. This confuses me, or I
missed something here?

Many thanks,
Jun

             reply	other threads:[~2008-05-13  3:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  3:32 Jun Koi [this message]
2008-05-13 17:59 ` [Qemu-devel] understanding how arpl is translated Fabrice Bellard
2008-05-15 10:11   ` Jun Koi

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=fdaac4d50805122032j4923a2fbs7fc5ab4aeabb30cc@mail.gmail.com \
    --to=junkoi2004@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).