From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Reconsidering special return statements (with SmPL)?
Date: Sun, 17 Nov 2024 21:30:28 +0100 [thread overview]
Message-ID: <78dd11f0-b07a-4a3e-ab42-4534e4e4ce73@web.de> (raw)
In-Reply-To: <d577a3b9-d43-19d3-15cf-2b11fb1ce59f@inria.fr>
>> Would you like to become able to handle such source code places also
>> by the means of the semantic patch language?
>>
>> @display@
>> @@
>> *return ...;
>> *return ...;
>
> What is the problem here?
It seems that this source code search approach points known data processing challenges out
(also according to a specific function implementation example).
https://elixir.bootlin.com/linux/v6.12-rc7/source/drivers/power/reset/as3722-poweroff.c#L55
How good does a desire for dead code avoidance fit to the current development status
of computation tree logic variants?
Regards,
Markus
prev parent reply other threads:[~2024-11-17 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 9:26 [cocci] Reconsidering special return statements (with SmPL)? Markus Elfring
2024-11-17 16:04 ` Julia Lawall
2024-11-17 20:30 ` 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=78dd11f0-b07a-4a3e-ab42-4534e4e4ce73@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@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).