tor/scripts/coccinelle/try_parse.sh

#!/bin/sh

# Echo the name of every argument of this script that is not "perfect"
# according to coccinelle's --parse-c.

top="$(dirname "$0")/../.."

exitcode=0

for fn in "$@"; do

    if spatch -macro_file_builtins "$top"/scripts/coccinelle/tor-coccinelle.h \
              -I "$top" -I "$top"/src -I "$top"/ext --defined COCCI \
              --parse-c "$fn" \
              2>/dev/null | grep "perfect = 1" > /dev/null; then
        : # it's perfect
    else
        echo "$fn"
        if test "${VERBOSE}" != ""; then
            spatch -macro_file_builtins "$top"/scripts/coccinelle/tor-coccinelle.h \
                   -I "$top" -I "$top"/src -I "$top"/ext --defined COCCI \
                   --parse-c "$fn"
        fi
        exitcode=1
    fi

done

exit "$exitcode"
Add a script to tell whether a file can be perfectly parsed by spatch spatch can let us know whether a file has parsed "perfectly" or not. The more perfect it parses, the likelier any semantic patches are to apply. I've used this script to identify problem areas in our code. 2019-09-12 00:44:10 +02:00			`#!/bin/sh`

			`# Echo the name of every argument of this script that is not "perfect"`
			`# according to coccinelle's --parse-c.`

			`top="$(dirname "$0")/../.."`

try_parse.sh: add a verbose mode and a meaningful exit code. 2019-10-09 15:31:10 +02:00			`exitcode=0`

Add a script to tell whether a file can be perfectly parsed by spatch spatch can let us know whether a file has parsed "perfectly" or not. The more perfect it parses, the likelier any semantic patches are to apply. I've used this script to identify problem areas in our code. 2019-09-12 00:44:10 +02:00			`for fn in "$@"; do`

			`if spatch -macro_file_builtins "$top"/scripts/coccinelle/tor-coccinelle.h \`
Add a "COCCI" macro that we tell coccinelle is always defined. This will let us give specific in-file equivalents to given macros or preprocessor directives, to make things parse. 2019-10-09 16:07:50 +02:00			`-I "$top" -I "$top"/src -I "$top"/ext --defined COCCI \`
			`--parse-c "$fn" \`
Add a script to tell whether a file can be perfectly parsed by spatch spatch can let us know whether a file has parsed "perfectly" or not. The more perfect it parses, the likelier any semantic patches are to apply. I've used this script to identify problem areas in our code. 2019-09-12 00:44:10 +02:00			`2>/dev/null \| grep "perfect = 1" > /dev/null; then`
			`: # it's perfect`
			`else`
			`echo "$fn"`
try_parse.sh: add a verbose mode and a meaningful exit code. 2019-10-09 15:31:10 +02:00			`if test "${VERBOSE}" != ""; then`
			`spatch -macro_file_builtins "$top"/scripts/coccinelle/tor-coccinelle.h \`
Add a "COCCI" macro that we tell coccinelle is always defined. This will let us give specific in-file equivalents to given macros or preprocessor directives, to make things parse. 2019-10-09 16:07:50 +02:00			`-I "$top" -I "$top"/src -I "$top"/ext --defined COCCI \`
			`--parse-c "$fn"`
try_parse.sh: add a verbose mode and a meaningful exit code. 2019-10-09 15:31:10 +02:00			`fi`
			`exitcode=1`
Add a script to tell whether a file can be perfectly parsed by spatch spatch can let us know whether a file has parsed "perfectly" or not. The more perfect it parses, the likelier any semantic patches are to apply. I've used this script to identify problem areas in our code. 2019-09-12 00:44:10 +02:00			`fi`

			`done`
try_parse.sh: add a verbose mode and a meaningful exit code. 2019-10-09 15:31:10 +02:00
			`exit "$exitcode"`