qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PULL 0/6] tricore patches for 2.3
Date: Mon, 16 Mar 2015 16:02:54 +0000	[thread overview]
Message-ID: <1426521780-31653-1-git-send-email-kbastian@mail.uni-paderborn.de> (raw)

Hi Peter,

here are my last tricore patches for this release, which finish up all the 
integer instructions (with the exception of trap related instructions). I hope 
it's okay if I squeeze them into this release.

Cheers,
Bastian 

The following changes since commit 307146cb9359ad6d4544e00af073088772d165eb:

  Merge remote-tracking branch 'remotes/kvaneesh/for-upstream' into staging (2015-03-16 13:04:09 +0000)

are available in the git repository at:

  https://github.com/bkoppelmann/qemu-tricore-upstream.git tags/pull-tricore-20150316

for you to fetch changes up to b724b012a4ea9877c5ddad254df63735a945618c:

  target-tricore: Add instructions of SYS opcode format (2015-03-16 15:53:08 +0000)

----------------------------------------------------------------
TriCore RRR1, RRRR, RRRW, and SYS instructions

----------------------------------------------------------------
Bastian Koppelmann (6):
      target-tricore: Add instructions of RRR1 opcode format, which have 0xa3 as first opcode
      target-tricore: Add instructions of RRR1 opcode format, which have 0x63 as first opcode
      target-tricore: Add instructions of RRR1 opcode format, which have 0xe3 as first opcode
      target-tricore: Add instructions of RRRR opcode format
      target-tricore: Add instructions of RRRW opcode format
      target-tricore: Add instructions of SYS opcode format

 target-tricore/cpu.h             |    7 +
 target-tricore/helper.h          |   12 +
 target-tricore/op_helper.c       |  436 +++
 target-tricore/translate.c       | 6767 +++++++++++++++++++++++---------------
 target-tricore/tricore-opcodes.h |   56 +-
 5 files changed, 4526 insertions(+), 2752 deletions(-)
-- 
2.3.3

             reply	other threads:[~2015-03-16 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 16:02 Bastian Koppelmann [this message]
2015-03-16 16:02 ` [Qemu-devel] [PULL 1/6] target-tricore: Add instructions of RRR1 opcode format, which have 0xa3 as first opcode Bastian Koppelmann
2015-03-16 16:02 ` [Qemu-devel] [PULL 2/6] target-tricore: Add instructions of RRR1 opcode format, which have 0x63 " Bastian Koppelmann
2015-03-16 16:02 ` [Qemu-devel] [PULL 3/6] target-tricore: Add instructions of RRR1 opcode format, which have 0xe3 " Bastian Koppelmann
2015-03-16 16:02 ` [Qemu-devel] [PULL 4/6] target-tricore: Add instructions of RRRR opcode format Bastian Koppelmann
2015-03-16 16:02 ` [Qemu-devel] [PULL 5/6] target-tricore: Add instructions of RRRW " Bastian Koppelmann
2015-03-16 16:03 ` [Qemu-devel] [PULL 6/6] target-tricore: Add instructions of SYS " Bastian Koppelmann
2015-03-16 19:18 ` [Qemu-devel] [PULL 0/6] tricore patches for 2.3 Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2015-03-03  1:18 Bastian Koppelmann
2015-03-08  6:42 ` 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=1426521780-31653-1-git-send-email-kbastian@mail.uni-paderborn.de \
    --to=kbastian@mail.uni-paderborn.de \
    --cc=peter.maydell@linaro.org \
    --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).