All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Comparing statement lists with SmPL
Date: Thu, 17 Aug 2017 19:54:08 +0200	[thread overview]
Message-ID: <c5f3c8db-e5ec-47c1-3d84-8392a7101645@users.sourceforge.net> (raw)
In-Reply-To: <be855581-e22e-2b58-8565-68412ae590b3@users.sourceforge.net>

>>> Can the search for duplicated source code be improved by the means of the
>>> semantic patch language?
>>
>> For two statements at least you could do:
> 
> An other SmPL script variant can work to some degree.

How do you think about the relevance of the SmPL construct ?<+... ...+>?
for this use case?


I tried my intermediate SmPL script variant a bit more.

Example:

elfring at Sonne:~/Projekte/Linux/next-patched> git checkout next-20170803 && spatch.opt ~/Projekte/Coccinelle/janitor/show_same_statements3.cocci fs/ubifs/lpt.c
?
@@ -1974,10 +1974,6 @@ again:
 		int ret, lnum = lprops->lnum;
 
 		ret = scan_cb(c, lprops, path[h].in_tree, data);
-		if (ret < 0) {
-			err = ret;
-			goto out;
-		}
 		if (ret & LPT_SCAN_ADD) {
 			/* Add all the nodes in path to the tree in memory */
 			for (h = 1; h < c->lpt_hght; h++) {


Now I wonder how this test result should fit to my source code search pattern.
I find also more results questionable for this Linux software module.
It seems that there are only two functions which would be an acceptable match.

Regards,
Markus

  reply	other threads:[~2017-08-17 17:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 17:26 [Cocci] Comparing statement lists with SmPL SF Markus Elfring
2017-08-15 17:33 ` Julia Lawall
2017-08-15 19:04   ` SF Markus Elfring
2017-08-15 19:09     ` Julia Lawall
2017-08-15 19:14       ` SF Markus Elfring
2017-08-15 20:00     ` SF Markus Elfring
2017-08-15 20:09       ` Julia Lawall
2017-08-15 20:15         ` SF Markus Elfring
2017-08-16  6:48         ` SF Markus Elfring
2017-08-16  7:03           ` SF Markus Elfring
2017-08-16  9:20             ` Julia Lawall
2017-08-16 10:42               ` SF Markus Elfring
2017-08-16  9:01           ` Julia Lawall
2017-08-16  7:35         ` SF Markus Elfring
2017-08-17 17:54           ` SF Markus Elfring [this message]
2017-08-17 18:44             ` Julia Lawall
2017-08-17 19:26               ` SF Markus Elfring
2017-08-17 19:31                 ` Julia Lawall
2017-08-17 19:43                   ` SF Markus Elfring
2017-08-22  9:19                   ` SF Markus Elfring
2017-08-22  9:28                     ` Julia Lawall
2017-08-22 10:00                       ` SF Markus Elfring
     [not found]                         ` <alpine.DEB.2.20.1708221202380.3178@hadrien>
2017-08-22 10:12                           ` SF Markus Elfring
2017-08-22 10:15                             ` Julia Lawall
2017-08-22 10:20                               ` SF Markus Elfring
     [not found]                                 ` <alpine.DEB.2.20.1708221221260.3178@hadrien>
2017-08-22 10:33                                   ` SF Markus Elfring
2017-08-23 14:43                     ` SF Markus Elfring
     [not found]                       ` <alpine.DEB.2.20.1708231644340.3150@hadrien>
2017-08-23 15:39                         ` SF Markus Elfring
     [not found]                           ` <alpine.DEB.2.20.1708231742480.3150@hadrien>
2017-08-23 15:50                             ` SF Markus Elfring
2017-08-24  7:56                             ` SF Markus Elfring
2017-08-16  6:10   ` SF Markus Elfring
2017-08-16  6:26     ` Julia Lawall
2017-08-16  6:38       ` SF 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=c5f3c8db-e5ec-47c1-3d84-8392a7101645@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=cocci@systeme.lip6.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.