qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Questions/comments on TCG
Date: Fri, 7 Mar 2008 19:55:59 +0000	[thread overview]
Message-ID: <20080307195559.GA30601@miranda.arrow> (raw)
In-Reply-To: <f43fc5580803071047l34c7f507m375939ac6fa8f834@mail.gmail.com>

On Fri, Mar 07, 2008 at 08:47:03PM +0200, Blue Swirl wrote:
> On 3/7/08, Stuart Brady <sdbrady@ntlworld.com> wrote:
> > tcg_target_reg_alloc_order[] has 32 elements, but only 14 are used.
> >  The rest hold 0, specifying TCG_REG_G0.
> 
> I see. That could be asking for trouble.

Possibly not, as g0 is marked as reserved, but it looks to me like bug,
regardless of whether it causes any harm, so I've submitted a patch.

> > I don't understand -- o7 is required when returning in exit_tb, so if it
> >  is used, it must be saved and restored.
> 
> Not exit_tb, but call.

Right, op_call does need to link, and that clobbers the link register,
so it must be restored -- but I've a feeling that this isn't happening.
I expect you could copy o7 to/from i5 before/after the call (or jmpl)...
although I'm not sure if you'd also need to save the frame pointer.

op_exit_tb also needs the link register, as it needs to know where to
return to.  I see you've fixed op_goto_tb -- I'm not sure if TCG_REG_I5
now needs removing from tcg_target_reg_alloc_order[], though.

Cheers,
-- 
Stuart Brady

  reply	other threads:[~2008-03-07 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 12:37 [Qemu-devel] Questions/comments on TCG Stuart Brady
2008-03-07 16:07 ` Blue Swirl
2008-03-07 18:19   ` Stuart Brady
2008-03-07 18:47     ` Blue Swirl
2008-03-07 19:55       ` Stuart Brady [this message]
2008-03-07 20:30         ` Blue Swirl
2008-03-08 14:07           ` Blue Swirl
2008-03-07 18:28 ` [Qemu-devel] [PATCH] Remove blank elements in tcg_target_reg_alloc_order[] 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=20080307195559.GA30601@miranda.arrow \
    --to=sdbrady@ntlworld.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).