From: Blue Swirl <blauwirbel@gmail.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Weil <stefan@mail.berlios.de>
Subject: Re: [Qemu-devel] [PATCH] tcg, tci: Add TCG and interpreter for bytecode (virtual machine)
Date: Mon, 28 Sep 2009 21:42:27 +0300 [thread overview]
Message-ID: <f43fc5580909281142i6d8f8541id1917ee31bfc3f6f@mail.gmail.com> (raw)
In-Reply-To: <1254156621-28559-1-git-send-email-weil@mail.berlios.de>
On Mon, Sep 28, 2009 at 7:50 PM, Stefan Weil <weil@mail.berlios.de> wrote:
> This is an initial and highly experimental version of
> a new code generator which does not create native code
> (so it will not depend on the host running qemu when it
> is finished). It creates bytecode which is interpreted.
>
> The current version can run the bios code, a simple
> hello world and the linux-user testcode for the
> i386 and x86_64 targets on x86_64 hosts.
>
> Some additional information is in tcg/bytecode/README
> which is part of the patch.
>
> Please send patches / enhancements based on my latest
> version from git://repo.or.cz/qemu/ar7.git.
Nice. When the interpreter works, it should be unconditional for
targets that are not supported by TCG.
> +QEMU can create native code for some hosts (arm, hppa, i386, ppc, ppc64,
> +sparc, x86_64). For others, inoffical host support was written (s390).
unofficial
> +static const int tcg_target_call_oarg_regs[2] = {
> + // TODO: ppc64 only uses one register. Why do others use two?
To pass a 64 bit return value in two 32 bit registers?
> +static const char * const tcg_target_reg_names[TCG_TARGET_NB_REGS] = {
> +#if TCG_TARGET_NB_REGS == 16 || TCG_TARGET_NB_REGS == 32
> + "r16",
Table overflow.
next prev parent reply other threads:[~2009-09-28 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 16:50 [Qemu-devel] [RFC] tcg/interpreter: Add TCG + interpreter for bytecode (virtual machine) Stefan Weil
2009-09-28 16:50 ` [Qemu-devel] [PATCH] tcg, tci: Add TCG and " Stefan Weil
2009-09-28 18:42 ` Blue Swirl [this message]
2009-09-28 21:33 ` Stefan Weil
2009-10-04 18:27 ` Stuart Brady
2009-10-11 16:33 ` Stefan Weil
2009-10-11 16:55 ` malc
2009-10-11 21:04 ` malc
2009-10-26 15:26 ` Stefan Weil
2009-10-26 15:52 ` malc
2009-10-11 23:17 ` Stuart Brady
2009-10-11 23:50 ` malc
2009-10-12 6:46 ` Stuart Brady
2009-10-12 12:33 ` malc
2009-10-12 12:55 ` malc
2009-10-12 17:39 ` Stuart Brady
2009-10-12 20:07 ` malc
2009-10-12 20:30 ` Stuart Brady
2010-05-12 19:06 ` [Qemu-devel] [RFC] tcg/interpreter: Add TCG + " Stefan Weil
2010-05-13 2:01 ` Jun Koi
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=f43fc5580909281142i6d8f8541id1917ee31bfc3f6f@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefan@mail.berlios.de \
--cc=weil@mail.berlios.de \
/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).