qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [RFD] TCG context
Date: Tue, 2 Dec 2008 16:23:39 +0100	[thread overview]
Message-ID: <761ea48b0812020723w57f64c1fn3c0c033b7350a0f8@mail.gmail.com> (raw)

Hello,

a few months ago I proposed a patch that puts gen_opc_ptr and
gen_opparam_ptr into TCG context:

http://lists.gnu.org/archive/html/qemu-devel/2008-07/msg00869.html

After discussing with Fabrice, it's useless without getting rid of the
global TCG context variable.  I fully agree with him.

Obviously getting rid of TCG context variable means passing it as a
parameter to every TCG function which is a rather intrusive and
painful task, though it's mechanical enough that introducing bugs
is not a concern.

I also think that some of the other global variables could benefit
from being put into that context (e.g., gen_opc_buf,
gen_opparam_buf).  That could come later and is much less
intrusive.

I have done all of that for my own needs for one target.

Are some people interested enough that I make this for all
targets?


Laurent

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=761ea48b0812020723w57f64c1fn3c0c033b7350a0f8@mail.gmail.com \
    --to=laurent.desnogues@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).