qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <ltaylorsimpson@gmail.com>
To: "'Philippe Mathieu-Daudé'" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: <brian.cain@oss.qualcomm.com>, <quic_mathbern@quicinc.com>,
	<sidneym@quicinc.com>, <quic_mliebel@quicinc.com>,
	<richard.henderson@linaro.org>, <ale@rev.ng>, <anjo@rev.ng>
Subject: RE: [PATCH] Hexagon (target/hexagon) Remove gen_tcg_func_table.py
Date: Wed, 16 Apr 2025 08:58:29 -0600	[thread overview]
Message-ID: <075601dbaee0$05faee40$11f0cac0$@gmail.com> (raw)
In-Reply-To: <074e01dbaede$2516b720$6f442560$@gmail.com>



> -----Original Message-----
> From: ltaylorsimpson@gmail.com <ltaylorsimpson@gmail.com>
> Sent: Wednesday, April 16, 2025 8:45 AM
> To: 'Philippe Mathieu-Daudé' <philmd@linaro.org>; qemu-
> devel@nongnu.org
> Cc: brian.cain@oss.qualcomm.com; quic_mathbern@quicinc.com;
> sidneym@quicinc.com; quic_mliebel@quicinc.com;
> richard.henderson@linaro.org; ale@rev.ng; anjo@rev.ng
> Subject: RE: [PATCH] Hexagon (target/hexagon) Remove
> gen_tcg_func_table.py
> 
> 
> 
> > -----Original Message-----
> > From: Philippe Mathieu-Daudé <philmd@linaro.org>
> > Sent: Wednesday, April 16, 2025 12:18 AM
> > To: Taylor Simpson <ltaylorsimpson@gmail.com>; qemu-
> devel@nongnu.org
> > Cc: brian.cain@oss.qualcomm.com; quic_mathbern@quicinc.com;
> > sidneym@quicinc.com; quic_mliebel@quicinc.com;
> > richard.henderson@linaro.org; ale@rev.ng; anjo@rev.ng
> > Subject: Re: [PATCH] Hexagon (target/hexagon) Remove
> > gen_tcg_func_table.py
> >
> > Hi Taylor,
> >
> > On 16/4/25 01:55, Taylor Simpson wrote:
> > > This can easily be done in C with opcodes_def_generated.h.inc
> > >
> > > Signed-off-by: Taylor Simpson <ltaylorsimpson@gmail.com>
> > > ---
> > >   target/hexagon/genptr.c              |  6 ++-
> > >   target/hexagon/README                |  1 -
> > >   target/hexagon/gen_tcg_func_table.py | 66 ----------------------------
> > >   target/hexagon/meson.build           | 10 -----
> > >   4 files changed, 5 insertions(+), 78 deletions(-)
> > >   delete mode 100755 target/hexagon/gen_tcg_func_table.py
> > >
> > > diff --git a/target/hexagon/gen_tcg_func_table.py
> > > b/target/hexagon/gen_tcg_func_table.py
> > > deleted file mode 100755
> > > index 299a39b1aa..0000000000
> > > --- a/target/hexagon/gen_tcg_func_table.py
> > > -        f.write("const SemanticInsn opcode_genptr[XX_LAST_OPCODE] =
> > {\n")
> > > -        for tag in hex_common.tags:
> > > -            ## Skip the priv instructions
> > > -            if "A_PRIV" in hex_common.attribdict[tag]:
> > > -                continue
> > > -            ## Skip the guest instructions
> > > -            if "A_GUEST" in hex_common.attribdict[tag]:
> > > -                continue
> > > -            ## Skip the diag instructions
> > > -            if tag == "Y6_diag":
> > > -                continue
> > > -            if tag == "Y6_diag0":
> > > -                continue
> > > -            if tag == "Y6_diag1":
> > > -                continue
> >
> > What about all these skipped tags? IIUC gen_opcodes_def.py doesn't
> > skip them. If it isn't necessary to skip, please mention it in the
> > commit description for clarity.
> >
> > Regards,
> >
> > Phil.

I looked into this.  There aren't any instructions currently in the code that would be skipped by this logic.  Perhaps this logic was needed at one point in time but is no longer needed because those instructions were removed at some point.

I recall that Brian consolidated the logic to decide which instructions to skip into a single function in hex_common.py as part of the system mode patch series.  So, I'll go ahead and add a comment to the commit description as you suggest.

Thanks,
Taylor




  reply	other threads:[~2025-04-16 14:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 23:55 [PATCH] Hexagon (target/hexagon) Remove gen_tcg_func_table.py Taylor Simpson
2025-04-16  6:18 ` Philippe Mathieu-Daudé
2025-04-16 14:45   ` ltaylorsimpson
2025-04-16 14:58     ` ltaylorsimpson [this message]
2025-04-17  7:09       ` Philippe Mathieu-Daudé
2025-04-17 15:55     ` Brian Cain

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='075601dbaee0$05faee40$11f0cac0$@gmail.com' \
    --to=ltaylorsimpson@gmail.com \
    --cc=ale@rev.ng \
    --cc=anjo@rev.ng \
    --cc=brian.cain@oss.qualcomm.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quic_mathbern@quicinc.com \
    --cc=quic_mliebel@quicinc.com \
    --cc=richard.henderson@linaro.org \
    --cc=sidneym@quicinc.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).