From: Greg Dietsche <gregory.dietsche@cuw.edu>
To: Julia Lawall <julia@diku.dk>
Cc: Gilles.Muller@lip6.fr, npalix.work@gmail.com, cocci@diku.dk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coccinelle: if(ret)return ret; return ret; semantic patch
Date: Sat, 11 Jun 2011 10:37:14 -0500 [thread overview]
Message-ID: <4DF38BAA.9050406@cuw.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.1106060651320.7113@ask.diku.dk>
On 06/05/2011 11:55 PM, Julia Lawall wrote:
> Thanks. I tried this too, but I wasn't sure about the results. The
> question is why stop here. For example, there are IS_ERR calls that one
> could consider as well. Or ret< 0. Or why not just:
>
> @@
> expression ret;
> @@
>
> - if (...) return ret;
> return ret;
>
>
I've been thinking a bit more about this. Is there a community
preference towards patches that are highly reliable v.s. ones that find
things that might not be a problem? I'm leaning towards updating my
patch to do the above and then later coming back when I have more time
to fix it up to find only things that are really problems.
Greg
> Although there might be function calls that one doesn't want to touch, so:
>
> @@
> identifier f != IS_ERR;
> expression ret;
> statement S;
> @@
>
> (
> if (<+...f(...)...+>) S
> |
> - if (...) return ret;
> return ret;
> )
>
> julia
>
>
> On Sun, 5 Jun 2011, Greg Dietsche wrote:
>
>
>> This semantic patch finds code matching this pattern:
>> if(ret)
>> return ret;
>> return ret;
>>
>> I will be submitting patches shortly against the mainline to cleanup all
>> code matching this pattern.
>>
>> Signed-off-by: Greg Dietsche<Gregory.Dietsche@cuw.edu>
>> ---
>> scripts/coccinelle/misc/doublereturn.cocci | 20 ++++++++++++++++++++
>> 1 files changed, 20 insertions(+), 0 deletions(-)
>> create mode 100644 scripts/coccinelle/misc/doublereturn.cocci
>>
>> diff --git a/scripts/coccinelle/misc/doublereturn.cocci b/scripts/coccinelle/misc/doublereturn.cocci
>> new file mode 100644
>> index 0000000..656a118
>> --- /dev/null
>> +++ b/scripts/coccinelle/misc/doublereturn.cocci
>> @@ -0,0 +1,20 @@
>> +/// Remove unecessary if/return in code that follows this pattern:
>> +/// if(retval)
>> +/// return retval;
>> +/// return retval;
>> +//
>> +// Confidence: High
>> +// Copyright: (C) 2011 Greg Dietsche GPLv2.
>> +// URL: http://www.gregd.org
>> +// Comments:
>> +// Options: -no_includes
>> +
>> +virtual patch
>> +
>> +@@
>> +identifier retval;
>> +@@
>> +-if (retval)
>> +- return retval;
>> +-return retval;
>> ++return retval;
>> --
>> 1.7.2.5
>>
>>
>>
>
next prev parent reply other threads:[~2011-06-11 15:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 0:26 [PATCH] coccinelle: if(ret)return ret; return ret; semantic patch Greg Dietsche
2011-06-06 4:55 ` Julia Lawall
2011-06-07 15:47 ` Greg Dietsche
2011-06-07 16:56 ` Julia Lawall
2011-06-07 21:54 ` Nicolas Palix
2011-06-07 22:59 ` Greg Dietsche
2011-06-08 7:11 ` Nicolas Palix
2011-06-08 7:24 ` Julia Lawall
2011-06-11 15:37 ` Greg Dietsche [this message]
2011-06-11 15:43 ` Julia Lawall
2011-06-06 4:56 ` Julia Lawall
2011-06-13 18:23 ` [PATCH v2] coccinelle: if (ret) return " Greg Dietsche
2011-06-13 18:36 ` Joe Perches
2011-06-13 18:38 ` Julia Lawall
2011-06-13 20:55 ` Greg Dietsche
2011-06-14 5:50 ` Julia Lawall
2011-06-14 21:24 ` Greg Dietsche
2011-06-15 1:15 ` Greg Dietsche
2011-06-15 5:58 ` Julia Lawall
2011-06-15 15:33 ` [Cocci] " Greg Dietsche
2011-06-15 15:34 ` Julia Lawall
2011-06-15 15:35 ` Julia Lawall
2011-06-15 16:05 ` Greg Dietsche
2011-06-15 1:29 ` [PATCH v3] " Greg Dietsche
2011-06-15 5:50 ` Julia Lawall
2011-06-15 15:50 ` [PATCH v4] " Greg Dietsche
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=4DF38BAA.9050406@cuw.edu \
--to=gregory.dietsche@cuw.edu \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix.work@gmail.com \
/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.