From: Markus Elfring <Markus.Elfring@web.de>
To: "Gábor Szeder" <szeder.dev@gmail.com>
Cc: "René Scharfe" <l.s.r@web.de>, "Jeff King" <peff@peff.net>,
git@vger.kernel.org
Subject: Re: coccinelle: improve array.cocci
Date: Fri, 22 Nov 2019 17:17:56 +0100 [thread overview]
Message-ID: <c9cc76dc-615f-ff89-6305-64d897734a4a@web.de> (raw)
In-Reply-To: <20191122152950.GZ23183@szeder.dev>
> I did try --jobs on a couple of occasions,
Thanks for your feedback.
> and the results always varied between broken, not working,
The parallelisation support by the Coccinelle software was questionable
for a while.
> or downright making things even slower.
I wonder about this information.
…
> spatch version 1.0.4 with Python support and with PCRE support
…
> Fatal error: exception Sys_error("array: No such file or directory")
Another bit of background information:
* https://lore.kernel.org/cocci/99082e9d-8047-eee3-68dd-9849868d4a96@users.sourceforge.net/
https://systeme.lip6.fr/pipermail/cocci/2016-August/003546.html
* https://lore.kernel.org/cocci/alpine.DEB.2.10.1506171707190.2578@hadrien/
https://systeme.lip6.fr/pipermail/cocci/2015-June/002141.html
…
> Therefore, merely passing in '--jobs <N>' doesn't bring any runtime benefits:
This program parameter should be used for other command variants.
…
> It appears that batching 'spatch' invocations with 1.0.8 does not
> bring the same benefits as with 1.0.4, but brings slowdowns instead...
Would you like to share your experiences also on the Coccinelle mailing list?
Regards,
Markus
next prev parent reply other threads:[~2019-11-22 16:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 15:08 coccinelle: adjustments for array.cocci? Markus Elfring
2019-11-12 18:37 ` René Scharfe
2019-11-13 2:11 ` Junio C Hamano
2019-11-13 8:49 ` Markus Elfring
2019-11-14 2:03 ` Junio C Hamano
2019-11-14 13:15 ` Markus Elfring
2019-11-14 16:41 ` René Scharfe
2019-11-14 17:14 ` Markus Elfring
2019-11-14 17:46 ` René Scharfe
2019-11-15 11:11 ` git-coccinelle: " Markus Elfring
2019-11-15 14:20 ` Markus Elfring
2019-11-15 18:50 ` Markus Elfring
2019-11-16 1:00 ` [Cocci] " Julia Lawall
2019-11-16 6:57 ` Markus Elfring
2019-11-16 8:29 ` Markus Elfring
2019-11-16 17:57 ` Julia Lawall
2019-11-16 18:29 ` Markus Elfring
2019-11-15 20:37 ` coccinelle: " Markus Elfring
2019-11-16 21:13 ` René Scharfe
2019-11-17 7:56 ` Markus Elfring
2019-11-17 13:40 ` René Scharfe
2019-11-17 18:19 ` Markus Elfring
2019-11-19 19:14 ` René Scharfe
2019-11-19 20:21 ` Markus Elfring
2019-11-21 19:01 ` René Scharfe
2019-11-16 16:33 ` Markus Elfring
2019-11-16 21:38 ` René Scharfe
2019-11-17 8:19 ` Markus Elfring
2019-11-17 13:40 ` René Scharfe
2019-11-17 18:36 ` Markus Elfring
2019-11-19 19:15 ` René Scharfe
2019-11-18 16:10 ` [PATCH] coccinelle: improve array.cocci Markus Elfring
2019-11-19 19:15 ` René Scharfe
2019-11-20 9:01 ` Markus Elfring
2019-11-21 19:02 ` René Scharfe
2019-11-21 19:44 ` Markus Elfring
2019-11-22 15:29 ` SZEDER Gábor
2019-11-22 16:17 ` Markus Elfring [this message]
2019-11-22 5:54 ` [PATCH] " Junio C Hamano
2019-11-22 7:34 ` Markus Elfring
2020-01-25 8:23 ` Markus Elfring
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=c9cc76dc-615f-ff89-6305-64d897734a4a@web.de \
--to=markus.elfring@web.de \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=szeder.dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).