From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: [Qemu-devel] [PATCH 4/5] tcg/sparc: Only one call output register needed for 64 bit hosts
Date: Mon, 5 Sep 2011 11:07:01 +0200 [thread overview]
Message-ID: <1315213622-7051-5-git-send-email-weil@mail.berlios.de> (raw)
In-Reply-To: <1315213622-7051-1-git-send-email-weil@mail.berlios.de>
The second register is only needed for 32 bit hosts.
Cc: Blue Swirl <blauwirbel@gmail.com>
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
tcg/sparc/tcg-target.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/tcg/sparc/tcg-target.c b/tcg/sparc/tcg-target.c
index ac76e11..fc3fd7f 100644
--- a/tcg/sparc/tcg-target.c
+++ b/tcg/sparc/tcg-target.c
@@ -84,9 +84,11 @@ static const int tcg_target_call_iarg_regs[6] = {
TCG_REG_O5,
};
-static const int tcg_target_call_oarg_regs[2] = {
+static const int tcg_target_call_oarg_regs[] = {
TCG_REG_O0,
- TCG_REG_O1,
+#if TCG_TARGET_REG_BITS == 32
+ TCG_REG_O1
+#endif
};
static inline int check_fit_tl(tcg_target_long val, unsigned int bits)
--
1.7.0.4
next prev parent 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 [Qemu-devel] [PATCH 0/5] Only one call output register needed for 64 bit hosts Stefan Weil
2011-09-05 9:06 ` [Qemu-devel] [PATCH 1/5] tcg/i386: " 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 ` Stefan Weil [this message]
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-5-git-send-email-weil@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).