qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: mrolnik@gmail.com
Subject: [PATCH v2 0/3] target/avr: Convert to TranslatorOps
Date: Sun, 20 Jun 2021 14:50:19 -0700	[thread overview]
Message-ID: <20210620215022.1510617-1-richard.henderson@linaro.org> (raw)

I've reached a point where *all* targets must use the translator loop.  

Changes for v2:
  * Fix (drop) singlestep check for max_insns.
    We already do that generically.
  * Fully initialize DisasContext.

It was that last that caused the check-acceptance regression for v1.
I simply got lucky the first time (with optimization) and the
uninitialized struct members happened to have some zeros.


r~


Richard Henderson (3):
  target/avr: Add DisasContextBase to DisasContext
  target/avr: Change ctx to DisasContext* in gen_intermediate_code
  target/avr: Convert to TranslatorOps

 target/avr/translate.c | 284 ++++++++++++++++++++++-------------------
 1 file changed, 154 insertions(+), 130 deletions(-)

-- 
2.25.1



             reply	other threads:[~2021-06-20 21:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20 21:50 Richard Henderson [this message]
2021-06-20 21:50 ` [PATCH v2 1/3] target/avr: Add DisasContextBase to DisasContext Richard Henderson
2021-06-21 18:17   ` Philippe Mathieu-Daudé
2021-06-20 21:50 ` [PATCH v2 2/3] target/avr: Change ctx to DisasContext* in gen_intermediate_code Richard Henderson
2021-06-21 18:19   ` Philippe Mathieu-Daudé
2021-06-20 21:50 ` [PATCH v2 3/3] target/avr: Convert to TranslatorOps Richard Henderson
2021-06-21  5:38   ` Michael Rolnik
2021-06-21  8:33     ` Philippe Mathieu-Daudé
2021-06-21  8:38       ` Michael Rolnik

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=20210620215022.1510617-1-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=mrolnik@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).