From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Cc: Olaf Hering <olaf@aepfle.de>
Subject: [cocci] Reconsider software dependencies for PCRE support (with SmPL)
Date: Sun, 18 May 2025 10:50:30 +0200 [thread overview]
Message-ID: <55052f14-dbe4-467c-a7a4-41ce5fc1cc99@web.de> (raw)
Hello,
I got into the mood to try another script variant out (like the following) for
the semantic patch language.
// See also:
// update candidate: c4iw_rdev_open()
// https://elixir.bootlin.com/linux/v6.15-rc6/source/drivers/infiniband/hw/cxgb4/device.c#L908-L909
@Delete_unnecessary_checks@
expression x;
@@
if (...
- && x
)
kfree(x);
Such SmPL code does not use features according to regular expressions.
But I observed the following test result with the software combination
“Coccinelle 1.3-00083-g4093aad2d” on my openSUSE Tumbleweed system.
Markus_Elfring@Sonne:…/Projekte/Coccinelle/janitor> spatch --parse-cocci delete_unnecessary_checks7.cocci
spatch: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory
Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> spatch --version
spatch: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory
Under which circumstances can the corresponding software dependencies become
up-to-date again?
Regards,
Markus
next reply other threads:[~2025-05-18 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 8:50 Markus Elfring [this message]
2025-05-18 8:56 ` [cocci] Reconsider software dependencies for PCRE support (with SmPL) Julia Lawall
2025-05-19 9:44 ` Victor Gambier
2025-05-19 15:50 ` Markus Elfring
2025-05-21 11:56 ` Markus Elfring
2025-05-21 12:14 ` Olaf Hering
2025-05-21 12:24 ` Markus Elfring
2025-05-21 11:58 ` Victor Gambier
2025-05-21 12:18 ` Markus Elfring
2025-05-22 6:46 ` 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=55052f14-dbe4-467c-a7a4-41ce5fc1cc99@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=olaf@aepfle.de \
/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).