From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH, RFC] Update qemu-tech.texi, needs verification
Date: Sun, 5 Oct 2008 14:26:21 +0200 [thread overview]
Message-ID: <20081005122621.GA18592@edgar.se.axis.com> (raw)
In-Reply-To: <f43fc5580810050144t7f1d6d15ie006558f63f10953@mail.gmail.com>
On Sun, Oct 05, 2008 at 11:44:47AM +0300, Blue Swirl wrote:
> Hi,
>
> Currently qemu-tech.texi is no longer in synch with QEMU development.
> There are obsoleted references to code copying and dyngen versions,
> TCG has changed a lot regarding code generation and target/host status
> is no longer accurate.
>
> In this patch I've tried to update the document based on my
> understanding of how stuff works and what is the status of various
> targets. Please comment.
Hello Blue,
Great that somebody updates the docs!
I've got a comment:
@node Condition code optimisations
@section Condition code optimisations
@@ -343,15 +363,20 @@
the condition codes are not needed by the next instructions, no
condition codes are computed at all.
+This optimization is not yet implemented on other targets.
+
At least CRIS does something similar, I guess it's not as nice as the one for x86 but it's there :)
Thanks
next prev parent reply other threads:[~2008-10-05 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 8:44 [Qemu-devel] [PATCH, RFC] Update qemu-tech.texi, needs verification Blue Swirl
2008-10-05 12:26 ` Edgar E. Iglesias [this message]
2008-10-05 12:55 ` Thiemo Seufer
2008-10-05 17:28 ` malc
2008-10-06 13:26 ` Paul Brook
2008-10-06 17:53 ` Blue Swirl
2008-10-06 18:02 ` Paul Brook
2008-10-06 18:19 ` Laurent Desnogues
2008-10-06 19:09 ` andrzej zaborowski
2008-10-10 6:56 ` Kirill A. Shutemov
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=20081005122621.GA18592@edgar.se.axis.com \
--to=edgar.iglesias@axis.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).