From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: Re: [cocci] Avoiding duplicate elements in SmPL disjunctions?
Date: Sat, 22 Nov 2025 11:35:35 +0100 [thread overview]
Message-ID: <7cea8a1d-31ad-4475-be80-ef1cb1e3b2d1@web.de> (raw)
In-Reply-To: <228c50a2-bb15-4abe-bef9-b0f9b95f6992@web.de>
> An element of the generated SmPL disjunction got repeated somehow.
> How do you think about to avoid such duplicate code?
Will another data representation trigger more desirable improvements?
Markus_Elfring@Sonne:…/Projekte/Coccinelle/janitor> /usr/bin/spatch --parse-cocci show_unlimited_while_loops.cocci | sort | uniq -c -d
…
2 *while *(*1*)
Markus_Elfring@Sonne:~> /usr/bin/spatch --parse-cocci --sp '! 2' | sort | uniq -c -d
…
3 *0 *== *2
3 *!*2
3 *2 *== *0
Which components of the Coccinelle software are responsible for such
data processing results?
Regards,
Markus
next prev parent reply other threads:[~2025-11-22 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 9:50 [cocci] Avoiding duplicate elements in SmPL disjunctions? Markus Elfring
2025-11-22 10:35 ` Markus Elfring [this message]
[not found] ` <188e41fa-91c5-b09c-51d1-8f69f5d8cea@inria.fr>
2025-11-22 14:54 ` Markus Elfring
2025-11-23 10:00 ` Markus Elfring
[not found] ` <c23ff4fa-b44e-f653-8015-9c573ae2ad47@inria.fr>
2025-11-23 10:15 ` Markus Elfring
2026-08-25 16:32 ` Markus Elfring
2026-08-25 16:40 ` Julia Lawall
2026-08-25 19:27 ` Markus Elfring
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=7cea8a1d-31ad-4475-be80-ef1cb1e3b2d1@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 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.