On Fri, 19 Feb 2021, Denis Efremov wrote:
> Check for opencoded min(), max() implementations.
>
> Signed-off-by: Denis Efremov <efre...@linux.com>
> ---
>
> Changes in v2:
> - <... ...> instead of ... when any
> - org mode reports fixed
> - patch rule to drop excessive ()
>
> scripts/coccinelle/misc/minmax.cocci | 224 +++++++++++++++++++++++++++
> 1 file changed, 224 insertions(+)
> create mode 100644 scripts/coccinelle/misc/minmax.cocci
>
> diff --git a/scripts/coccinelle/misc/minmax.cocci
> b/scripts/coccinelle/misc/minmax.cocci
> new file mode 100644
> index 000000000000..61d6b61fd82c
> --- /dev/null
> +++ b/scripts/coccinelle/misc/minmax.cocci
> @@ -0,0 +1,224 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +///
> +/// Check for opencoded min(), max() implementations.
> +/// Generated patches sometimes require adding a cast to fix compile warning.
> +/// Warnings/patches scope intentionally limited to a function body.
> +///
> +// Confidence: Medium
> +// Copyright: (C) 2021 Denis Efremov ISPRAS
> +// Options: --no-includes --include-headers
> +//
> +// Keywords: min, max
> +//
> +
> +
> +virtual report
> +virtual org
> +virtual context
> +virtual patch
> +
> +@rmax depends on !patch@
> +identifier func;
> +expression x, y;
> +binary operator cmp = {>, >=};
> +position p;
> +@@
> +
> +func(...)
> +{
> + <...
> +* x cmp@p y ? x : y
The rule below indicated with FIXME is supposed to deal with the
possibility of () that are unnecessary when using min and max. It doesn't
work, because <... P ...> allow P to match 0 or more times, and thus
func@p matches every function.
A simpler solution is to just allow arbitrary () in the pattern, eg:
(x) cmp@p (y) ? (x) : (y)
That will allow each occurrence of x and y to occur with and without
parentheses. In the submitted semantic patch, the () issue was only
considered in the patch case. But it actually affects the purely matching
cases too, because () can be used at one occurrence, but not the other.
> +@script:python depends on report@
> +p << rmax.p;
> +@@
> +
> +coccilib.report.print_report(p[0], "WARNING opportunity for max()")
p is an array because it can be bound to different positions on different
control-flow paths. Notably this occurs with <... ...>. If there are
multiple occurrences of the pattern, there will be one match that contains
all of them. Thus the reporting code should be:
for p0 in p:
coccilib.report.print_report(p0, "WARNING opportunity for max()")
julia
