Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Release tracking for the Coccinelle project

Release of coccinelle-1.0.0-rc24

* Previously, it was possible to declare a metavariable to match only a
local variable, by saying "local idexpression x;".  Now it is also
possible to match a global variable, by saying "global expression x;".

* By default, when a semantic patch changes a function header, eg adding
new parameter, Coccinelle generates a corresponding rule for changing the
function prototype.  It is now possible to disable this behavior, by
putting disable prototypes in the rule header.

* Varargs.  It is now possible to match and transform functions that have
varargs in their parameter list.  Because of the conflict with the ...
notation of Coccinelle, the ... of C is written ...... (6 dots) in a
semantc patch.

* Inline in function prototypes.  These were not previously allowed in
semantic patch code.

* #ifdef on kernel version.  Previously these were always considered to be
comments.  Now they are treated like other #ifdefs.  Specifically, if such
an ifdef is around complete statements, the control flow will behave as
for an if.

* Parallelism in Coccinelle.  The following is an extract from the
option documentation:

--jobs <int>: Run the specified number of jobs in parallel. Can be
abbreviated as -j. This option is not compatible with the use of an
initialize or finalize rule in the semantic patch. This option furthermore
creates a temporary directory in the directory from which spatch is
executed that has the name of the semantic patch (without its extension)
and that contains stdout and stderr files generated by the various
processes. When the semantic patch completes, the contents of these files
are printed to standard output and standard error, respectively, and the
directory is removed.

--chunksize <int>. The specified number of files are dispatched as a
single unit of parallelism. This option is only interesting with the
options --all-includes or --recursive-includes, when combined with the
option --include-headers-for-types. In this case, parsed header files are
cached. It is only the files that are treated within a single chunk that
can benefit from this cache, due to the lack of shared memory in ocaml.
latest commit 4d09daa67a
Coccinelle authored rrhansen committed
Failed to load latest commit information.
bundles Release of coccinelle-1.0.0-rc24
commons Release of coccinelle-1.0.0-rc24
ctl Release of coccinelle-1.0.0-rc23
demos Version 1.0.0-rc21 has been released. The main changes are as follows:
docs Release of coccinelle-1.0.0-rc24
editors Release coccinelle-0.2.3rc1
engine Release of coccinelle-1.0.0-rc24
extra Release of coccinelle-1.0.0-rc23
globals Release of coccinelle-1.0.0-rc23
ocaml Release of coccinelle-1.0.0-rc24
parsing_c Release of coccinelle-1.0.0-rc24
parsing_cocci Release of coccinelle-1.0.0-rc24
popl Release of coccinelle-1.0.0-rc23
popl09 Release of coccinelle-1.0.0-rc24
python Release of coccinelle-1.0.0-rc24
scripts Release coccinelle-1.0.0-rc22
setup Coccinelle release 1.0.0-rc19
tests Release of coccinelle-1.0.0-rc24
tools Release of coccinelle-1.0.0-rc24
Makefile Release of coccinelle-1.0.0-rc24
Makefile.am - Try to do better pretty printing when array elements are individually
Makefile.common Release of coccinelle-1.0.0-rc23
Makefile.config.in Release of coccinelle-1.0.0-rc23
Makefile.dev Release of coccinelle-1.0.0-rc23
Makefile.libs Release of coccinelle-1.0.0-rc24
Makefile.release Release of coccinelle-1.0.0-rc23
_tags - Try to do better pretty printing when array elements are individually
authors.txt Release coccinelle-0.2.3rc3
bugs.txt Coccinelle release 1.0.0-rc19
changes.txt Release of coccinelle-1.0.0-rc24
cocci.ml Release of coccinelle-1.0.0-rc24
cocci.mli Release of coccinelle-1.0.0-rc24
configure Release of coccinelle-1.0.0-rc24
configure.ac Release of coccinelle-1.0.0-rc23
copyright.txt Release coccinelle-0.2.1-rc1
credits.txt Release coccinelle-0.1.7
empty.h
empty.iso
env.csh Release coccinelle-0.2.0rc1
env.sh Release coccinelle-0.2.3rc2
flag_cocci.ml Release coccinelle-1.0.0-rc22
install.txt Version 1.0.0-rc20 is now available at http://coccinelle.lip6.fr/down…
license.txt Release coccinelle-0.1
main.ml Release of coccinelle-1.0.0-rc24
myocamlbuild.ml.in - Try to do better pretty printing when array elements are individually
readme.txt Coccinelle release 1.0.0-rc19
release.nix - Try to do better pretty printing when array elements are individually
standard.h Version 1.0.0-rc20 is now available at http://coccinelle.lip6.fr/down…
standard.iso Release of coccinelle-1.0.0-rc24
testing.ml.in Release of coccinelle-1.0.0-rc23
testing.mli Release coccinelle-1.0.0-rc22
version Release of coccinelle-1.0.0-rc24
version.ml.in Coccinelle release 1.0.0-rc13

readme.txt

                            Coccinelle 


Coccinelle allows programmers to easily write some complex
style-preserving source-to-source transformations on C source code,
like for instance to perform some refactorings.

To install Coccinelle from its source, see the instructions in install.txt.
Once you have installed coccinelle, there is a script 'spatch' in /usr/bin
or /usr/local/bin that invokes the Coccinelle program.

If you want to run Coccinelle without installing it, you can run the
Coccinelle program directly from the download/build directory. You may then
have to setup a few environment variables so that the Coccinelle program
knows where to find its configuration files.
For bash do:

  $ source env.sh

For tcsh do:

  $ source env.csh 


You can test coccinelle with:

  $ spatch -sp_file demos/simple.cocci demos/simple.c -o /tmp/new_simple.c

If you haven't installed coccinelle, run then ./spatch or ./spatch.opt 



If you downloaded the bytecode version of spatch you may first 
have to install OCaml (which contains the 'ocamlrun' bytecode interpreter,
the equivalent of 'java', the Java virtual machine, but for OCaml) and then do:

  $ ocamlrun spatch -sp_file demos/simple.cocci demos/simple.c -o /tmp/new_simple.c


For more information on Coccinelle, type 'make docs' and have a look at the 
files in the docs/ directory. You may need to install the texlive-fonts-extra
packages from your distribution to compile some of the LaTeX documentation
files.

 ** Runtime dependencies under Debian/Ubuntu**

 - For the OCaml scripting feature in SmPL
	ocaml-native-compilers
     or ocaml-nox

---------------------------------------------------------------------------

Contributing:

Contributions are welcome.  Please sign your contributions, according to
the following text extracted from Documentation/SubmittingPatches.txt of
the Linux kernel:

The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as an open-source patch.  The rules are pretty simple: if you
can certify the below:

        Developer's Certificate of Origin 1.1

        By making a contribution to this project, I certify that:

        (a) The contribution was created in whole or in part by me and I
            have the right to submit it under the open source license
            indicated in the file; or

        (b) The contribution is based upon previous work that, to the best
            of my knowledge, is covered under an appropriate open source
            license and I have the right under that license to submit that
            work with modifications, whether created in whole or in part
            by me, under the same open source license (unless I am
            permitted to submit under a different license), as indicated
            in the file; or

        (c) The contribution was provided directly to me by some other
            person who certified (a), (b) or (c) and I have not modified
            it.

	(d) I understand and agree that this project and the contribution
	    are public and that a record of the contribution (including all
	    personal information I submit with it, including my sign-off) is
	    maintained indefinitely and may be redistributed consistent with
	    this project or the open source license(s) involved.

then you just add a line saying

	Signed-off-by: Random J Developer <random@developer.example.org>

using your real name (sorry, no pseudonyms or anonymous contributions.)
Something went wrong with that request. Please try again.