[Cocci] Coccinelle: fix parallel build with CHECK=scripts/coccicheck

SF Markus Elfring elfring at users.sourceforge.net
Tue Nov 14 13:31:26 CET 2017

> The goal is that the user can easily find the stdou and stderr information
> while the semantic patch is running.

It matters when the tool “spatch” tries to apply its own parallelisation strategy.

> This is useful for long running semantic patches to see
> if things are going well or not.

Yes, of course.

> I decided on creating a directory that contains the name of the semantic
> patch, then the date, then the pid.

I imagine that time stamps and process identifiers can become fragile.

> It should be easy for the user to see which is the most recent,
> in the case that previous instances are remaining.

This is usually fine.

> The goal is to avoid getting a mysterious error from make coccicheck,
> not to meet the needs of advanced users.

* How advanced are they if they pass the parameter “CHECK=scripts/coccicheck”?

* The Linux make script will be improved so that extra parallelisation
  will be usually avoided by the Coccinelle software.


More information about the Cocci mailing list