qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brian Cain <brian.cain@oss.qualcomm.com>
To: Taylor Simpson <ltaylorsimpson@gmail.com>
Cc: qemu-devel@nongnu.org, matheus.bernardino@oss.qualcomm.com,
	sid.manning@oss.qualcomm.com, marco.liebel@oss.qualcomm.com,
	richard.henderson@linaro.org, philmd@linaro.org, ale@rev.ng,
	anjo@rev.ng
Subject: Re: [PATCH 0/4] Clean up end-of-instruction processing
Date: Tue, 9 Dec 2025 13:18:27 -0600	[thread overview]
Message-ID: <CAEqNhNYM_uqUHK6M_dg49xw4B41+KRV6DHq9P9shM_EoEcStug@mail.gmail.com> (raw)
In-Reply-To: <20251114230013.158098-1-ltaylorsimpson@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On Fri, Nov 14, 2025 at 5:00 PM Taylor Simpson <ltaylorsimpson@gmail.com>
wrote:

> The changes to packet processing have made some of the end-of-instruction
> processing obsolete.  With the addition of gen_analyze_funcs.py and the
> ability to short-circuit a packet commit, we no longer need to "log" the
> register writes of each instruction.
>
> Taylor Simpson (4):
>   Hexagon (target/hexagon) Remove gen_log_reg_write
>   Hexagon (target/hexagon) s/gen_log_pred_write/gen_pred_write
>   Hexagon (target/hexagon) s/gen_log_vreg_write/gen_vreg_write
>   Hexagon (target/hexagon) s/log_write/gen_write
>

These commits are now queued for post-10.2 (11.0?) at
https://github.com/quic/qemu/commits/hex-next-express/

Thanks!



>
>  target/hexagon/gen_tcg.h                    | 11 ++-
>  target/hexagon/genptr.h                     |  3 +-
>  target/hexagon/genptr.c                     | 86 +++++++++------------
>  target/hexagon/idef-parser/parser-helpers.c |  4 +-
>  target/hexagon/README                       | 10 ++-
>  target/hexagon/gen_tcg_funcs.py             |  3 +-
>  target/hexagon/hex_common.py                | 56 +++++++-------
>  7 files changed, 77 insertions(+), 96 deletions(-)
>
> --
> 2.43.0
>
>

[-- Attachment #2: Type: text/html, Size: 2209 bytes --]

      parent reply	other threads:[~2025-12-09 19:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 23:00 [PATCH 0/4] Clean up end-of-instruction processing Taylor Simpson
2025-11-14 23:00 ` [PATCH 1/4] Hexagon (target/hexagon) Remove gen_log_reg_write Taylor Simpson
2025-12-03 23:34   ` Brian Cain
2025-11-14 23:00 ` [PATCH 2/4] Hexagon (target/hexagon) s/gen_log_pred_write/gen_pred_write Taylor Simpson
2025-11-17 17:35   ` Philippe Mathieu-Daudé
2025-12-03 23:36   ` Brian Cain
2025-11-14 23:00 ` [PATCH 3/4] Hexagon (target/hexagon) s/gen_log_vreg_write/gen_vreg_write Taylor Simpson
2025-11-17 17:36   ` Philippe Mathieu-Daudé
2025-12-03 23:37   ` Brian Cain
2025-11-14 23:00 ` [PATCH 4/4] Hexagon (target/hexagon) s/log_write/gen_write Taylor Simpson
2025-11-17 17:37   ` Philippe Mathieu-Daudé
2025-12-03 23:37   ` Brian Cain
2025-11-17  9:28 ` [PATCH 0/4] Clean up end-of-instruction processing Philippe Mathieu-Daudé
2025-11-17 17:08   ` Brian Cain
2025-11-17 17:35     ` Philippe Mathieu-Daudé
2025-11-17 18:35     ` Taylor Simpson
2025-11-17 20:02       ` Taylor Simpson
2025-12-04  8:46       ` Philippe Mathieu-Daudé
2025-12-09 19:18 ` Brian Cain [this message]

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=CAEqNhNYM_uqUHK6M_dg49xw4B41+KRV6DHq9P9shM_EoEcStug@mail.gmail.com \
    --to=brian.cain@oss.qualcomm.com \
    --cc=ale@rev.ng \
    --cc=anjo@rev.ng \
    --cc=ltaylorsimpson@gmail.com \
    --cc=marco.liebel@oss.qualcomm.com \
    --cc=matheus.bernardino@oss.qualcomm.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sid.manning@oss.qualcomm.com \
    /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).