All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Froyd <froydnj@codesourcery.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 1/2] target-arm: Move Neon VUZP to a helper function
Date: Fri, 11 Feb 2011 09:03:47 -0800	[thread overview]
Message-ID: <20110211170346.GP6247@codesourcery.com> (raw)
In-Reply-To: <AANLkTimJwF2+be=TVTDSkjp0=X14oam1kwF2d_zCFcGH@mail.gmail.com>

On Fri, Feb 11, 2011 at 04:53:30PM +0000, Peter Maydell wrote:
> On 11 February 2011 16:14, Peter Maydell <peter.maydell@linaro.org> wrote:
> > +void HELPER(neon_unzip)(CPUState *env, uint32_t insn)
> > +{
> > +    int rd = ((insn >> 18) & 0x10) | ((insn >> 12) & 0x0f);
> > +    int rm = ((insn >> 1) & 0x10) | (insn & 0x0f);
> > +    int size = (insn >> 18) & 3;
> > +    if (insn & 0x40) { /* Q */
> > +        uint64_t zm0 = float64_val(env->vfp.regs[rm]);
> > +        uint64_t zm1 = float64_val(env->vfp.regs[rm + 1]);
> > +        uint64_t zd0 = float64_val(env->vfp.regs[rd]);
> > +        uint64_t zd1 = float64_val(env->vfp.regs[rd + 1]);
> 
> I can rework these patches if people don't like the way this is
> effectively doing decoding in a helper function, incidentally,
> although I'm not convinced it would end up any nicer overall.

I do think the preferred way would be to extract rd, rm, size, and Q
up-front, rather than having the helper twiddle instruction bits.

-Nathan

  reply	other threads:[~2011-02-11 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 16:13 [Qemu-devel] [PATCH 0/2] target-arm: fix Neon VUZP, VZIP instructions Peter Maydell
2011-02-11 16:14 ` [Qemu-devel] [PATCH 1/2] target-arm: Move Neon VUZP to a helper function Peter Maydell
2011-02-11 16:53   ` Peter Maydell
2011-02-11 17:03     ` Nathan Froyd [this message]
2011-02-11 17:12       ` Peter Maydell
2011-02-11 17:14         ` Nathan Froyd
2011-02-11 16:14 ` [Qemu-devel] [PATCH 2/2] target-arm: Move Neon VZIP " Peter Maydell

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=20110211170346.GP6247@codesourcery.com \
    --to=froydnj@codesourcery.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --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.