qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <planche2k@googlemail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] TCG: 128 bit ops?
Date: Thu, 4 Sep 2008 13:10:39 +0200	[thread overview]
Message-ID: <D1F4A45F-4F7A-477E-8045-4886C45949BA@gmail.com> (raw)

Hello,

Am I correct in seeing that TCG offers no i128 ops? Would this be  
useful to add to TCG, internally reusing the i64/i32 code? ppc needs  
128-bit temporaries for Altivec instructions. It uses a union  
ppc_avr_t of (among others) two uint64_t.

Or should I just use two i64 temporaries with a local macro/helper?
It's not used much in ppc but I thought it might be useful to share  
with other architectures.

Andreas

             reply	other threads:[~2008-09-04 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 11:10 Andreas Färber [this message]
2008-09-04 14:35 ` [Qemu-devel] TCG: 128 bit ops? Aurelien Jarno
2008-09-04 15:30   ` Blue Swirl
2008-09-07 14:01 ` Paul Brook

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=D1F4A45F-4F7A-477E-8045-4886C45949BA@gmail.com \
    --to=planche2k@googlemail.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).