qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 0/5] Only one call output register needed for 64 bit hosts
Date: Mon,  5 Sep 2011 11:06:57 +0200	[thread overview]
Message-ID: <1315213622-7051-1-git-send-email-weil@mail.berlios.de> (raw)

The number of registers needed for the return value of TCG opcode
INDEX_op_call is calculated in function tcg_gen_callN (nb_rets).

It can be 0 or 1, for 32 bit hosts also 2 (return 64 bit value in
two 32 bit registers).

Some TCG implementations reserve 2 registers although only 1 is used.
The following patches fix this.

[PATCH 1/5] tcg/i386: Only one call output register needed for 64 bit hosts
[PATCH 2/5] tcg/ia64: Only one call output register needed for 64 bit hosts
[PATCH 3/5] tcg/s390: Only one call output register needed for 64 bit hosts
[PATCH 4/5] tcg/sparc: Only one call output register needed for 64 bit hosts
[PATCH 5/5] tcg/ppc64: Only one call output register needed for 64 bit hosts

             reply	other threads:[~2011-09-05  9:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05  9:06 Stefan Weil [this message]
2011-09-05  9:06 ` [Qemu-devel] [PATCH 1/5] tcg/i386: Only one call output register needed for 64 bit hosts Stefan Weil
2011-09-05  9:06 ` [Qemu-devel] [PATCH 2/5] tcg/ia64: " Stefan Weil
2011-09-05  9:07 ` [Qemu-devel] [PATCH 3/5] tcg/s390: " Stefan Weil
2011-09-07 11:32   ` Alexander Graf
2011-09-08  8:12     ` Richard Henderson
2011-09-05  9:07 ` [Qemu-devel] [PATCH 4/5] tcg/sparc: " Stefan Weil
2011-09-05  9:07 ` [Qemu-devel] [PATCH 5/5] tcg/ppc64: " Stefan Weil
2011-09-05 15:25   ` malc
2011-09-17 14:01 ` [Qemu-devel] [PATCH 0/5] " Stefan Weil
2011-09-17 18:51   ` 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=1315213622-7051-1-git-send-email-weil@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --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).