From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH 16/18] TCG/s390: use TCG_REG_CALL_STACK instead of TCG_REG_R15
Date: Sat, 28 May 2011 13:08:48 +0300 [thread overview]
Message-ID: <BANLkTi=8T3cqGVXWaef++7oC65WfgzrQ2Q@mail.gmail.com> (raw)
Use TCG_REG_CALL_STACK instead of TCG_REG_R15 for consistency.
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
---
tcg/s390/tcg-target.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/tcg/s390/tcg-target.c b/tcg/s390/tcg-target.c
index 2fc5646..e112052 100644
--- a/tcg/s390/tcg-target.c
+++ b/tcg/s390/tcg-target.c
@@ -2298,10 +2298,11 @@ static void tcg_target_init(TCGContext *s)
static void tcg_target_qemu_prologue(TCGContext *s)
{
/* stmg %r6,%r15,48(%r15) (save registers) */
- tcg_out_insn(s, RXY, STMG, TCG_REG_R6, TCG_REG_R15, TCG_REG_R15, 48);
+ tcg_out_insn(s, RXY, STMG, TCG_REG_R6, TCG_REG_CALL_STACK,
+ TCG_REG_CALL_STACK, 48);
/* aghi %r15,-160 (stack frame) */
- tcg_out_insn(s, RI, AGHI, TCG_REG_R15, -160);
+ tcg_out_insn(s, RI, AGHI, TCG_REG_CALL_STACK, -160);
if (GUEST_BASE >= 0x80000) {
tcg_out_movi(s, TCG_TYPE_PTR, TCG_GUEST_BASE_REG, GUEST_BASE);
@@ -2315,7 +2316,8 @@ static void tcg_target_qemu_prologue(TCGContext *s)
tb_ret_addr = s->code_ptr;
/* lmg %r6,%r15,208(%r15) (restore registers) */
- tcg_out_insn(s, RXY, LMG, TCG_REG_R6, TCG_REG_R15, TCG_REG_R15, 208);
+ tcg_out_insn(s, RXY, LMG, TCG_REG_R6, TCG_REG_CALL_STACK,
+ TCG_REG_CALL_STACK, 208);
/* br %r14 (return) */
tcg_out_insn(s, RR, BCR, S390_CC_ALWAYS, TCG_REG_R14);
--
1.6.2.4
next reply other threads:[~2011-05-28 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 10:08 Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-19 21:06 [Qemu-devel] [PATCH 16/18] TCG/s390: use TCG_REG_CALL_STACK instead of TCG_REG_R15 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='BANLkTi=8T3cqGVXWaef++7oC65WfgzrQ2Q@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).