From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 00/18] TCG stack frame patches
Date: Mon, 20 Jun 2011 00:04:20 +0300 [thread overview]
Message-ID: <BANLkTi=V-PBMANbVCkxC-Wr5UQQeL62X8g@mail.gmail.com> (raw)
I think x86 and Sparc patches are ready to be applied.
Blue Swirl (18):
Delegate setup of TCG temporaries to targets
TCG: fix negative frame offset calculations
TCG: remove broken stack allocation for call arguments
TCG/x86: use TCG_REG_CALL_STACK instead of TCG_REG_ESP
TCG/x86: use stack for TCG temps
TCG/Sparc64: use stack for TCG temps
TCG/ARM: use stack for TCG temps
TCG/HPPA: use TCG_REG_CALL_STACK instead of TCG_REG_SP
TCG/HPPA: use stack for TCG temps
TCG/IA64: use TCG_REG_CALL_STACK instead of TCG_REG_R12
TCG/IA64: use stack for TCG temps
TCG/MIPS: use TCG_REG_CALL_STACK instead of TCG_REG_SP
TCG/MIPS: use stack for TCG temps
TCG/PPC: use TCG_REG_CALL_STACK instead of TCG_REG_R1
TCG/PPC: use stack for TCG temps
TCG/s390: use TCG_REG_CALL_STACK instead of TCG_REG_R15
TCG/s390: use stack for TCG temps
Remove temp_buf, rename CPU_TEMP_BUF_NLONGS
cpu-defs.h | 3 ---
tcg/arm/tcg-target.c | 9 +++++++++
tcg/hppa/tcg-target.c | 35 +++++++++++++++++++++--------------
tcg/i386/tcg-target.c | 24 ++++++++++++++----------
tcg/ia64/tcg-target.c | 16 ++++++++++++----
tcg/mips/tcg-target.c | 18 +++++++++++-------
tcg/ppc/tcg-target.c | 22 +++++++++++++++-------
tcg/ppc64/tcg-target.c | 21 ++++++++++++++-------
tcg/s390/tcg-target.c | 11 ++++++++---
tcg/sparc/tcg-target.c | 5 ++++-
tcg/tcg.c | 21 ++++++++++++---------
tcg/tcg.h | 3 +++
translate-all.c | 2 --
13 files changed, 123 insertions(+), 67 deletions(-)
reply other threads:[~2011-06-19 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=V-PBMANbVCkxC-Wr5UQQeL62X8g@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).