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: kbastian@mail.uni-paderborn.de, david.brenken@efs-auto.de
Subject: [Qemu-devel] [PATCH 0/3] tricore: Convert to translate_loop
Date: Mon, 17 Jun 2019 16:35:30 +0200	[thread overview]
Message-ID: <20190617143533.15013-1-kbastian@mail.uni-paderborn.de> (raw)

Hi,

I finally came around to port TriCore to the "new" translate_loop
infrastructure. This is neccessary such that TriCore can be used in the upcoming
plugin API [1]. 

Cheers,
Bastian

[1] (https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg03165.html)


Bastian Koppelmann (3):
  target/tricore: Use DisasContextBase API
  target-tricore: Make env a member of DisasContext
  target/tricore: Use translate_loop

 target/tricore/translate.c | 527 +++++++++++++++++++------------------
 1 file changed, 272 insertions(+), 255 deletions(-)

-- 
2.22.0



             reply	other threads:[~2019-06-17 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 14:35 Bastian Koppelmann [this message]
2019-06-17 14:35 ` [Qemu-devel] [PATCH 1/3] target/tricore: Use DisasContextBase API Bastian Koppelmann
2019-06-17 16:06   ` Richard Henderson
2019-06-17 14:35 ` [Qemu-devel] [PATCH 2/3] target-tricore: Make env a member of DisasContext Bastian Koppelmann
2019-06-17 16:11   ` Richard Henderson
2019-06-17 14:35 ` [Qemu-devel] [PATCH 3/3] target/tricore: Use translate_loop Bastian Koppelmann
2019-06-17 16:45   ` Richard Henderson
2019-06-18 12:06     ` Bastian Koppelmann
2019-06-18 14:28       ` Richard Henderson
2019-06-17 16:51   ` Richard Henderson
2019-06-17 19:07 ` [Qemu-devel] [PATCH 0/3] tricore: Convert to translate_loop no-reply

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=20190617143533.15013-1-kbastian@mail.uni-paderborn.de \
    --to=kbastian@mail.uni-paderborn.de \
    --cc=david.brenken@efs-auto.de \
    --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).