cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Jaskaran Singh <jaskaran.singh@collabora.com>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [RFC PATCH 0/3] parsing_c: Optimize recursive header file parsing
Date: Wed, 9 Sep 2020 21:10:40 +0200	[thread overview]
Message-ID: <53573bbd-d550-b1b9-49f4-a84fabe20115@web.de> (raw)

> This patch series aims to optimize performance for recursively parsing
> header files in Coccinelle.

I am curious how you got encouraged to pick such a software development
challenge up.


> it would take close to 7 hours to complete.

This is unfortunate.

How do you think about to offer any more information (besides the
mentioned processor) for further benchmarking purposes?
https://github.com/coccinelle/coccinelle/issues/133


> The optimization that this patch series implements reduces that time to 1 hour.

Such a scale of improvement is impressive.


> - Skipping unparsable locations in header files: Skipping top-level items
>   in a header file that cannot be parsed. …

Will any further software evolution happen according to a topic like
“Exclusion of unsupported source code parts”?
https://github.com/coccinelle/coccinelle/issues/20


> - Recursively parse all header files only once and build a large type
>   environment. Use the dependency graph to determine reachability. …

Are you looking for the support of header file “precompilation”?

Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

             reply	other threads:[~2020-09-09 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 19:10 Markus Elfring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-09 18:12 [Cocci] [RFC PATCH 0/3] parsing_c: Optimize recursive header file parsing Jaskaran Singh

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=53573bbd-d550-b1b9-49f4-a84fabe20115@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=jaskaran.singh@collabora.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).