From: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>
To: qemu-devel@nongnu.org
Cc: tsimpson@quicinc.com, bcain@quicinc.com, quic_mliebel@quicinc.com
Subject: [PATCH v2 0/2] Hexagon: minor cleanups to comments and python scripts
Date: Wed, 24 May 2023 11:41:46 -0300 [thread overview]
Message-ID: <cover.1684939078.git.quic_mathbern@quicinc.com> (raw)
These are two minor follow ups to the last Hexagon pull, updating some
stale code comments and removing undefined variables at python scripts.
Changes in v2:
- Patch 1: adjusted get_regtags() to filter out the unused regs,
also removing the unused variables at the call sites.
- Patch 2: replaced outdated comments with pseudocode
v1: https://lore.kernel.org/qemu-devel/cover.1684873957.git.quic_mathbern@quicinc.com/
Matheus Tavares Bernardino (2):
target/hexagon/*.py: clean up used 'toss' and 'numregs' vars
Hexagon: fix outdated `hex_new_*` comments
target/hexagon/genptr.c | 26 +++++++-------
target/hexagon/translate.c | 2 +-
target/hexagon/gen_analyze_funcs.py | 10 +++---
target/hexagon/gen_helper_funcs.py | 30 ++++++++--------
target/hexagon/gen_helper_protos.py | 22 ++++++------
target/hexagon/gen_idef_parser_funcs.py | 4 +--
target/hexagon/gen_op_regs.py | 4 +--
target/hexagon/gen_tcg_funcs.py | 46 ++++++++++++-------------
target/hexagon/hex_common.py | 24 ++++++-------
9 files changed, 83 insertions(+), 85 deletions(-)
--
2.37.2
next reply other threads:[~2023-05-24 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 14:41 Matheus Tavares Bernardino [this message]
2023-05-24 14:41 ` [PATCH v2 1/2] target/hexagon/*.py: clean up used 'toss' and 'numregs' vars Matheus Tavares Bernardino
2023-05-24 16:42 ` Taylor Simpson
2023-05-24 14:41 ` [PATCH v2 2/2] Hexagon: fix outdated `hex_new_*` comments Matheus Tavares Bernardino
2023-05-24 16:43 ` Taylor Simpson
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=cover.1684939078.git.quic_mathbern@quicinc.com \
--to=quic_mathbern@quicinc.com \
--cc=bcain@quicinc.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_mliebel@quicinc.com \
--cc=tsimpson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.