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] [PATCH] simplify storing temporaries in env structure regardless of host/target long size
Date: Tue, 12 Feb 2008 21:12:16 +0200	[thread overview]
Message-ID: <f43fc5580802121112g751f3ad2j996ae80420dc15f6@mail.gmail.com> (raw)
In-Reply-To: <b2fa41d60802121052t457792fkddacd182a0517d85@mail.gmail.com>

On 2/12/08, Igor Kovalenko <igor.v.kovalenko@gmail.com> wrote:
> This patch separates decision about storing temporaries in env
> structure from target long size by introducing a macro
> QEMU_TEMPORARY_IN_ENV
> Makes it a bit easier to work around register allocation problems.
> By default there is no change to generated code.

I'd move env->t0/t1/t2 to CPU_COMMON and the T0/T1/T2 logic to
hostregs_helper.h.

  reply	other threads:[~2008-02-12 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 18:52 [Qemu-devel] [PATCH] simplify storing temporaries in env structure regardless of host/target long size Igor Kovalenko
2008-02-12 19:12 ` Blue Swirl [this message]
2008-02-12 19:25   ` Igor Kovalenko

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=f43fc5580802121112g751f3ad2j996ae80420dc15f6@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).