From: Gabriele Monaco <gmonaco@redhat.com>
To: Nam Cao <namcao@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] verification/rvgen: Do not generate unused variables
Date: Mon, 21 Jul 2025 14:07:15 +0200 [thread overview]
Message-ID: <87c5e103780e8d8d0cef27cb3cba69ab0bcb9b1f.camel@redhat.com> (raw)
In-Reply-To: <636b2b2d99a9bd46a9f77a078d44ebd7ffc7508c.1752850449.git.namcao@linutronix.de>
On Fri, 2025-07-18 at 16:58 +0200, Nam Cao wrote:
> ltl2k generates all variable definition in both ltl_start() and
> ltl_possible_next_states(). However, these two functions may not use
> all
> the variables, causing "unused variable" compiler warning.
>
> Change the script to only generate used variables.
>
> Signed-off-by: Nam Cao <namcao@linutronix.de>
Tried both patches and they seem to work as intended.
Reviewed-by: Gabriele Monaco <gmonaco@redhat.com>
Thanks,
Gabriele
> ---
> tools/verification/rvgen/rvgen/ltl2k.py | 25 +++++++++++++++++++++--
> --
> 1 file changed, 21 insertions(+), 4 deletions(-)
>
> diff --git a/tools/verification/rvgen/rvgen/ltl2k.py
> b/tools/verification/rvgen/rvgen/ltl2k.py
> index 59da351792ec..b075f98d50c4 100644
> --- a/tools/verification/rvgen/rvgen/ltl2k.py
> +++ b/tools/verification/rvgen/rvgen/ltl2k.py
> @@ -106,20 +106,25 @@ class ltl2k(generator.Monitor):
> ])
> return buf
>
> - def _fill_atom_values(self):
> + def _fill_atom_values(self, required_values):
> buf = []
> for node in self.ltl:
> - if node.op.is_temporal():
> + if str(node) not in required_values:
> continue
>
> if isinstance(node.op, ltl2ba.AndOp):
> buf.append("\tbool %s = %s && %s;" % (node,
> node.op.left, node.op.right))
> + required_values |= {str(node.op.left),
> str(node.op.right)}
> elif isinstance(node.op, ltl2ba.OrOp):
> buf.append("\tbool %s = %s || %s;" % (node,
> node.op.left, node.op.right))
> + required_values |= {str(node.op.left),
> str(node.op.right)}
> elif isinstance(node.op, ltl2ba.NotOp):
> buf.append("\tbool %s = !%s;" % (node,
> node.op.child))
> + required_values.add(str(node.op.child))
>
> for atom in self.atoms:
> + if atom.lower() not in required_values:
> + continue
> buf.append("\tbool %s = test_bit(LTL_%s, mon->atoms);" %
> (atom.lower(), atom))
>
> buf.reverse()
> @@ -135,7 +140,13 @@ class ltl2k(generator.Monitor):
> "ltl_possible_next_states(struct ltl_monitor *mon,
> unsigned int state, unsigned long *next)",
> "{"
> ]
> - buf.extend(self._fill_atom_values())
> +
> + required_values = set()
> + for node in self.ba:
> + for o in sorted(node.outgoing):
> + required_values |= o.labels
> +
> + buf.extend(self._fill_atom_values(required_values))
> buf.extend([
> "",
> "\tswitch (state) {"
> @@ -166,7 +177,13 @@ class ltl2k(generator.Monitor):
> "static void ltl_start(struct task_struct *task, struct
> ltl_monitor *mon)",
> "{"
> ]
> - buf.extend(self._fill_atom_values())
> +
> + required_values = set()
> + for node in self.ba:
> + if node.init:
> + required_values |= node.labels
> +
> + buf.extend(self._fill_atom_values(required_values))
> buf.append("")
>
> for node in self.ba:
prev parent reply other threads:[~2025-07-21 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 14:58 [PATCH 0/2] verification/rvgen: Fix variable definition generation Nam Cao
2025-07-18 14:58 ` [PATCH 1/2] verification/rvgen: Generate each variable definition only once Nam Cao
2025-07-18 14:58 ` [PATCH 2/2] verification/rvgen: Do not generate unused variables Nam Cao
2025-07-21 12:07 ` Gabriele Monaco [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=87c5e103780e8d8d0cef27cb3cba69ab0bcb9b1f.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namcao@linutronix.de \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®