From: Markus Elfring <Markus.Elfring@web.de>
To: "Derek M. Jones" <derek@knosof.co.uk>, cocci@inria.fr
Subject: Re: [cocci] Multiple returns significant performance impact
Date: Thu, 24 Oct 2024 18:48:25 +0200 [thread overview]
Message-ID: <db8a6990-f7ae-4e2b-b3a7-bd157fa7158e@web.de> (raw)
In-Reply-To: <3d11c8fb-6503-4a29-8889-03a91ca14088@knosof.co.uk>
>> Every position variable contains complete information about the enclosing
>
> Thanks. This will simplify the scripts.
Do you transfer any source code position information into higher level structures
so that you can eventually benefit more from parallel data processing?
Regards,
Markus
next prev parent reply other threads:[~2024-10-24 16:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 11:56 [cocci] Multiple returns significant performance impact Derek M Jones
2024-10-24 12:42 ` Markus Elfring
2024-10-24 14:48 ` Julia Lawall
2024-10-24 15:23 ` Derek M Jones
2024-10-24 15:29 ` Julia Lawall
2024-10-24 15:35 ` Derek M Jones
2024-10-24 15:38 ` Julia Lawall
2024-10-24 15:44 ` Victor Gambier
2024-10-24 16:00 ` Julia Lawall
2024-10-24 15:50 ` Derek M Jones
2024-10-24 16:07 ` Markus Elfring
2024-10-24 16:14 ` Julia Lawall
2024-10-24 16:48 ` Markus Elfring [this message]
2024-10-24 17:30 ` Derek M Jones
2024-10-24 18:26 ` Markus Elfring
2024-10-24 21:03 ` Derek M Jones
2024-10-25 5:38 ` Markus Elfring
2024-10-25 11:54 ` Derek M Jones
2024-10-27 12:48 ` [cocci] Broken code block size determination in function implementations Markus Elfring
2024-10-27 13:31 ` Julia Lawall
2024-10-27 15:15 ` Markus Elfring
2024-10-27 16:40 ` Markus Elfring
2024-10-27 17:05 ` Julia Lawall
2024-10-27 17:28 ` Markus Elfring
2024-10-27 17:34 ` Julia Lawall
2024-10-27 17:45 ` Markus Elfring
2024-10-27 17:55 ` Julia Lawall
2024-10-27 18:04 ` Markus Elfring
2024-10-27 18:00 ` Derek M Jones
2024-10-27 18:11 ` [cocci] Evolving experiences from evidence-based software engineering Markus Elfring
2024-10-28 9:00 ` [cocci] Searching for macro calls besides function implementations (with SmPL)? Markus Elfring
2024-10-28 12:57 ` Julia Lawall
2024-10-28 10:44 ` [cocci] Broken code block size determination in function implementations Markus Elfring
2024-10-29 12:17 ` Markus Elfring
2024-10-31 7:50 ` Markus Elfring
2024-10-26 11:43 ` [cocci] Checking SmPL run time characteristics for code block position " Markus Elfring
2024-10-24 16:16 ` [cocci] SmPL position variables … Markus Elfring
2024-10-24 16:20 ` Julia Lawall
2024-10-24 16:28 ` 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=db8a6990-f7ae-4e2b-b3a7-bd157fa7158e@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=derek@knosof.co.uk \
/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