From: Markus Elfring <Markus.Elfring@web.de>
To: "Julia Lawall" <julia.lawall@inria.fr>,
"Jérémy Lefaure" <jeremy.lefaure@netatmo.com>,
cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: [cocci] [PATCH v5] coccinelle: Extend address test from ifaddr semantic patch to test expressions
Date: Sat, 9 Jul 2022 07:30:57 +0200 [thread overview]
Message-ID: <612d0d85-9bfa-8dc2-8888-80eee1c8769f@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2207032345230.23263@hadrien>
>> This change aims at detecting an address test in more complex conditions
>> and not only in if statements.
…
>> v4 -> v5: Change semantic patch to match explicit tests to NULL +
>> improve commit message
…
>> Applied, thanks.
How do you think about to support more case distinctions for the discussed
source code search pattern (including also the detection and special handling
for pointer data types)?
@display disable decl_init@
type t;
statement is, es;
identifier i;
expression x, ix, ex, z;
binary operator bo;
@@
(
*if (&x)
is
else
es
|
* &x bo NULL
|
* NULL bo &x
|
* !(&x)
|
* (&x)
? ix
: ex
|
(
t* i = &x;
|
t* i;
... when != i = z
i = &x;
|
t i =
* (&x)
;
)
|
(z =
* (&x)
)
)
Regards,
Markus
prev parent reply other threads:[~2022-07-09 5:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 16:01 [cocci] [PATCH v5] coccinelle: Extend address test from ifaddr semantic patch to test expressions Jérémy LEFAURE
2022-07-01 16:55 ` Markus Elfring
2022-07-01 19:30 ` Markus Elfring
2022-07-01 20:49 ` Julia Lawall
2022-07-01 21:13 ` [cocci] [v5] " Markus Elfring
2022-07-02 8:01 ` [cocci] [PATCH v5] " Markus Elfring
2022-07-02 10:21 ` Julia Lawall
2022-07-02 11:00 ` [cocci] [v5] " Markus Elfring
2022-07-03 11:34 ` [cocci] [PATCH v5] " Markus Elfring
2022-07-03 10:50 ` Markus Elfring
2022-07-03 21:45 ` Julia Lawall
2022-07-04 17:16 ` [cocci] [v5] " Markus Elfring
2022-07-09 5: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=612d0d85-9bfa-8dc2-8888-80eee1c8769f@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=jeremy.lefaure@netatmo.com \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=nicolas.palix@imag.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).