qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Re: [PATCH, RFC, WIP] TCG for Qemu target Sparc32/64
Date: Sat, 23 Feb 2008 20:32:43 +0000	[thread overview]
Message-ID: <200802232032.44673.paul@codesourcery.com> (raw)
In-Reply-To: <47C064B5.4040809@bellard.org>

> Another point is that you should define TCG globals for each SPARC GPR.
> It was not done for i386 because I feared performance regressions when
> accessing to 16 bit or 8 bit sub-registers. On SPARC you do not have
> this issue.

How would these be kept consistent with CPUState?

Paul

  parent reply	other threads:[~2008-02-23 20:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 20:27 [Qemu-devel] [PATCH, RFC, WIP] TCG for Qemu target Sparc32/64 Blue Swirl
2008-02-22  0:06 ` Thiemo Seufer
2008-02-22 16:13   ` Blue Swirl
2008-02-23 18:23 ` [Qemu-devel] " Fabrice Bellard
2008-02-23 18:29   ` Blue Swirl
2008-02-23 18:48     ` Fabrice Bellard
2008-02-23 20:32   ` Paul Brook [this message]
2008-02-23 23:59   ` Stuart Brady

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=200802232032.44673.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=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).