qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PULL 00/11] sh4-next queue
Date: Fri, 12 Jun 2015 12:40:27 +0200	[thread overview]
Message-ID: <1434105638-642-1-git-send-email-aurelien@aurel32.net> (raw)

The following changes since commit b0411142f482df92717f8b4a3b746081a62b724f:

  Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20150609' into staging (2015-06-09 15:29:34 +0100)

are available in the git repository at:

  git://git.aurel32.net/qemu tags/pull-sh4-next-20150612

for you to fetch changes up to d218b28d28b8f4de297bfd35c082b22f153cf0df:

  target-sh4: remove dead code (2015-06-12 12:02:48 +0200)

----------------------------------------------------------------
sh4 linux-user cpu and hwcap
misc optimizations and cleanup
convert r2d to new MMIO accessor style

----------------------------------------------------------------
Aurelien Jarno (9):
      sh4/r2d: convert to new MMIO accessor style
      target-sh4: use bit number for SR constants
      target-sh4: Split out T from SR
      target-sh4: optimize addc using add2
      target-sh4: optimize subc using sub2
      target-sh4: optimize negc using add2 and sub2
      target-sh4: split out Q and M from of SR and optimize div1
      target-sh4: factorize fmov implementation
      target-sh4: remove dead code

Richard Henderson (2):
      linux-user: Default sh4 to sh7785
      linux-user: Add HWCAP for SH4

 hw/sh4/r2d.c           |  12 +-
 linux-user/elfload.c   |  29 +++++
 linux-user/main.c      |   2 +
 target-sh4/cpu.c       |   3 +-
 target-sh4/cpu.h       |  50 +++++---
 target-sh4/gdbstub.c   |   8 +-
 target-sh4/helper.c    |  29 ++---
 target-sh4/helper.h    |   1 -
 target-sh4/op_helper.c | 148 +---------------------
 target-sh4/translate.c | 327 ++++++++++++++++++++++++-------------------------
 10 files changed, 255 insertions(+), 354 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-06-12 10:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 10:40 Aurelien Jarno [this message]
2015-06-12 10:40 ` [Qemu-devel] [PULL 01/11] linux-user: Default sh4 to sh7785 Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 02/11] linux-user: Add HWCAP for SH4 Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 03/11] sh4/r2d: convert to new MMIO accessor style Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 04/11] target-sh4: use bit number for SR constants Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 05/11] target-sh4: Split out T from SR Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 06/11] target-sh4: optimize addc using add2 Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 07/11] target-sh4: optimize subc using sub2 Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 08/11] target-sh4: optimize negc using add2 and sub2 Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 09/11] target-sh4: split out Q and M from of SR and optimize div1 Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 10/11] target-sh4: factorize fmov implementation Aurelien Jarno
2015-06-12 10:40 ` [Qemu-devel] [PULL 11/11] target-sh4: remove dead code Aurelien Jarno
2015-06-12 14:38 ` [Qemu-devel] [PULL 00/11] sh4-next queue Peter Maydell

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=1434105638-642-1-git-send-email-aurelien@aurel32.net \
    --to=aurelien@aurel32.net \
    --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).