From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TCG native 32->64 concatenation
Date: Sun, 7 Sep 2008 21:15:13 +0300 [thread overview]
Message-ID: <f43fc5580809071115s1013a287tb31297f1620119f3@mail.gmail.com> (raw)
In-Reply-To: <200809071753.27384.paul@codesourcery.com>
On 9/7/08, Paul Brook <paul@codesourcery.com> wrote:
> The patch below adds a new concat_i32_i64 TCG op. This allows a pair of
> 32-bit values to be efficiently combined to form a 64-bit value. I've
> converted all the cases I could find to use this, and tested the arm code on
> both 32 and 64-bit hosts.
Sparc's helper_pack64 does the same thing, I used it to reduce
register pressure on i386 for 64 bit stores.
next prev parent reply other threads:[~2008-09-07 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 16:53 [Qemu-devel] TCG native 32->64 concatenation Paul Brook
2008-09-07 18:15 ` Blue Swirl [this message]
2008-09-07 18:43 ` Paul Brook
2008-09-14 17:03 ` Aurelien Jarno
2008-09-15 23:16 ` andrzej zaborowski
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=f43fc5580809071115s1013a287tb31297f1620119f3@mail.gmail.com \
--to=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).