From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: Re: [cocci] Fixing software for the movement of fwnode_handle_put() calls with SmPL
Date: Wed, 21 Feb 2024 16:34:45 +0100 [thread overview]
Message-ID: <bba73344-5c59-4e1c-9a42-f85decb534a9@web.de> (raw)
In-Reply-To: <755ceff5-2eca-433c-8cba-c0ac0d46b3fc@web.de>
…
> Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> time spatch --timeout 123 --show-trying pmic_glink_altmode-excerpt2-20240220.c ../janitor/adjust_exception_handling_in_pmic_glink_altmode-20240220.cocci
> …
> Fatal error: exception Coccinelle_modules.Common.Timeout
…
The amount of source code within a function implementation (like for this test example)
obviously influences the software run time also for the shown transformation attempt.
Thus the involved source code can be reduced for further software tests.
Finally, I could reproduce questionable software behaviour after a single
if statement (which contains a call of the function “dev_err_probe”) was left over
behind three other if statements.
Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> time spatch --timeout 5 pmic_glink_altmode-excerpt3-20240220.c ../janitor/adjust_exception_handling_in_pmic_glink_altmode-20240220.cocci
…
Fatal error: exception Coccinelle_modules.Common.Timeout
…
Will observations of “exploding” data processing run times trigger any improvements
for the discussed development tool?
Regards,
Markus
prev parent reply other threads:[~2024-02-21 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 14:05 [cocci] Moving fwnode_handle_put() calls to a single place with SmPL? Markus Elfring
2024-02-20 15:56 ` Markus Elfring
2024-02-21 12:08 ` Markus Elfring
2024-02-21 15:34 ` Markus Elfring [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=bba73344-5c59-4e1c-9a42-f85decb534a9@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).