From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Filip Navara <filip.navara@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] RFC: TCG ARM optimizations
Date: Mon, 29 Jun 2009 19:59:42 +0200 [thread overview]
Message-ID: <761ea48b0906291059g13103602uc678cc318ac63015@mail.gmail.com> (raw)
In-Reply-To: <5b31733c0906291050w355b2fe0n9ac6f62f3486e47c@mail.gmail.com>
On Mon, Jun 29, 2009 at 7:50 PM, Filip Navara<filip.navara@gmail.com> wrote:
>
> Big thanks goes to Laurent Desnogues who actually had suggested where
> the bottlenecks are.
IIRC it's Paul who suggested that idea first on IRC months
ago, as I was complaining about the stupidity of the generated
code :-)
Laurent
next prev parent reply other threads:[~2009-06-29 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 17:50 [Qemu-devel] [PATCH 0/3] RFC: TCG ARM optimizations Filip Navara
2009-06-29 17:59 ` Laurent Desnogues [this message]
2009-06-29 18:26 ` Filip Navara
2009-06-29 18:58 ` Blue Swirl
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=761ea48b0906291059g13103602uc678cc318ac63015@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=filip.navara@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).