On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
> I have a series of changes, and I want to only make a subsequent
> change if and only if at least one of a series of previous declared
> rules were matched. I can do this by depends on foo1 || foo2 || foo3
> || foo4, etc however since I have a lot
On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:43:57PM +0200, Wolfram Sang wrote:
> > > > Well, slightly better.
> > >
> > > No, it should be much better. You would have to look at the standard
> >
> > I use id-utils regularly and it is indeed at least a
On Sat, 11 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:51:26PM +0200, Wolfram Sang wrote:
> > > AFAICT coccinelle does not have integration support for id-utils though.
> >
> > I used it just today ;) -- "--use-idutils ./ID"
> >
> > ID was generated with simple 'mkid -s'.
> we should be able to also take advantage of with coccicheck,
> the most important one is paramap support.
Do OCaml developers prefer to refer to the software "Parmap" here?
https://rdicosmo.github.io/parmap/
Regards,
Markus
___
Cocci mailing list
> Also enable the load balancing to be dynamic, so that
> if a thread finishes early we keep feeding it.
Is this functionality influenced by the parameter "chunksize"?
Regards,
Markus
___
Cocci mailing list
Cocci@systeme.lip6.fr
> real16m11.692s
> user127m50.388s
> sys 0m2.168s
That's better but not a magnitude, I wonder.
signature.asc
Description: PGP signature
___
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
On Sat, 11 Jun 2016, SF Markus Elfring wrote:
> > Also enable the load balancing to be dynamic, so that
> > if a thread finishes early we keep feeding it.
>
> Is this functionality influenced by the parameter "chunksize"?
Yes, without chunksize the distribution of work to processes is static.
On Sat, 11 Jun 2016, Wolfram Sang wrote:
>
> > real16m11.692s
> > user127m50.388s
> > sys 0m2.168s
>
> That's better but not a magnitude, I wonder.
I think that it is because the filtering that Coccinelle does already
works pretty well, and there are quite a lot of files (7514)
> in practice though this seems to not perform better than
> regular grep however its expected to help with some use cases
> so we use that if you have no other indexing options in place
> available.
Would you like to fix a typo in this paragraph?
Regards,
Markus
> It's not as efficient as glimpse because the query language is simpler.
Interesting, what is missing compared to glimpse?
> So more filtering has to be done at the ocaml level. But it's probably
> fine in most cases.
For me, it has two advantages over glimpse:
a) it is in the debian
Glimpse is a tool you can use to index the kernel. The tool
was recently open sourced under the ISC license and can be
obtained at:
https://github.com/mcgrof/glimpse.git
Signed-off-by: Luis R. Rodriguez
---
scripts/glimpse.sh | 12
1 file changed, 12
coccicheck hasn't been updated for a while. The backports
project has been using some features for a while now that
we should be able to also take advantage of with coccicheck,
the most important one is paramap support.
glimpseindex stuff wasn't even building but today I decided
to go tackle and
Coccinelle has had paramap support since 1.0.2, this means
it supports --jobs, enabling built-in multithreaded functionality,
instead of needing one to script it out. Just look for --jobs
in the help output to determine if this is supported.
Also enable the load balancing to be dynamic, so that
Enable indexing optimizations heuristics. Coccinelle has
support to make use of its own enhanced "grep" mechanisms
instead of using regular grep for searching code 'coccigrep',
in practice though this seems to not perform better than
regular grep however its expected to help with some use cases
so
On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:02:38PM +0200, Julia Lawall wrote:
> >
> >
> > On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
> >
> > > Enable indexing optimizations heuristics. Coccinelle has
> > > support to make use of its own enhanced "grep"
On Fri, Jun 10, 2016 at 11:02:38PM +0200, Julia Lawall wrote:
>
>
> On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
>
> > Enable indexing optimizations heuristics. Coccinelle has
> > support to make use of its own enhanced "grep" mechanisms
> > instead of using regular grep for searching code
> > Well, slightly better.
>
> No, it should be much better. You would have to look at the standard
I use id-utils regularly and it is indeed at least a magnitude better.
The indexing often pays off already with the first coccinelle run for
me. Highly recommended.
signature.asc
Description:
> AFAICT coccinelle does not have integration support for id-utils though.
I used it just today ;) -- "--use-idutils ./ID"
ID was generated with simple 'mkid -s'.
signature.asc
Description: PGP signature
___
Cocci mailing list
Cocci@systeme.lip6.fr
On Sat, Jun 11, 2016 at 12:08:32AM +0200, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:51:26PM +0200, Wolfram Sang wrote:
> > > AFAICT coccinelle does not have integration support for id-utils though.
> >
> > I used it just today ;) -- "--use-idutils ./ID"
> >
> > ID was generated with
I have a series of changes, and I want to only make a subsequent
change if and only if at least one of a series of previous declared
rules were matched. I can do this by depends on foo1 || foo2 || foo3
|| foo4, etc however since I have a lot of rules I was hoping I could
condense these into one.
On Fri, Jun 10, 2016 at 11:43:57PM +0200, Wolfram Sang wrote:
> > > Well, slightly better.
> >
> > No, it should be much better. You would have to look at the standard
>
> I use id-utils regularly and it is indeed at least a magnitude better.
> The indexing often pays off already with the
21 matches
Mail list logo