From: Jacob Keller <jacob.e.keller@intel.com>
To: Markus Elfring <Markus.Elfring@web.de>, <cocci@inria.fr>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [cocci] behavior change in semantic patches since c36b51ffc889 …
Date: Mon, 10 Mar 2025 11:27:31 -0700 [thread overview]
Message-ID: <db753272-0294-4ea1-ad9f-bc210998267b@intel.com> (raw)
In-Reply-To: <26d75b7d-e9e1-4037-8f25-b8d93bd0950b@web.de>
On 3/8/2025 12:39 AM, Markus Elfring wrote:
>> I tried this out and it does seem to fix the white spacing for our
>> particular cases.
>
> Thanks for such positive feedback.
>
> Will your development interests grow also for further SmPL code variations?
>
>
>> From here, I just repeated the process until git bisect told me which
>> commit had the breaking change.
>
> How many iterations did you need to try out here?
>
About a dozen. Bisection is powerful because it scales with the
logarithm of the number of commits.
>
>> There were a couple gotchas where the checked out commit didn't compile
>> but I managed to figure out which changes were needed and manually
>> pulled those in each time.
>
> Do you see chances to improve such a process anyhow?
>
Most projects which use bisect heavily try to ensure that at least
compilation works with every change committed. This ensures that you can
build the project at any arbitrary commit in order to use the bisect
process.
>> One option would be to run a style formatting
>> tool after transforms, to allow a tool dedicated to code formatting vs
>> trying to make spatch and coccinelle do everything these can do.
>
> Are you looking for ways to avoid extra efforts for code reformatting?
>
In my experience, our existing coding style is not 100% replicated in
any of the formatting tools. It would take a significant effort to get
to the point where we could run a formatting tool without completely
re-formatting the entire code base.
>
>> I do think improvements in the way you can specify spacing would be
>> useful but may complicate the already difficult syntax of semantic patches.
> Adhering to code style requirements can be challenging.
>
Yep. I'm ok with some compromises, and we often have accepted those in
the past when adding new semantic patches.
However, this particular case is a change in the behavior of spatch,
which is a bit more difficult for us.
> Regards,
> Markus
next prev parent reply other threads:[~2025-03-10 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 0:43 [cocci] behavior change in semantic patches since c36b51ffc889 ("don't drop down on single statement") Jacob Keller
2025-03-07 0:55 ` Julia Lawall
2025-03-07 20:24 ` Jacob Keller
2025-03-07 10:47 ` [cocci] behavior change in semantic patches since c36b51ffc889 … Markus Elfring
2025-03-07 20:53 ` Jacob Keller
2025-03-07 22:47 ` Jacob Keller
2025-03-08 9:07 ` Markus Elfring
2025-03-10 18:34 ` Jacob Keller
2025-03-11 9:10 ` Markus Elfring
2025-03-08 8:39 ` Markus Elfring
2025-03-10 18:27 ` Jacob Keller [this message]
2025-03-11 9:26 ` Przemek Kitszel
2025-03-08 9:45 ` [cocci] Evolution of transformation processes? Markus Elfring
2025-03-10 18:23 ` Jacob Keller
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=db753272-0294-4ea1-ad9f-bc210998267b@intel.com \
--to=jacob.e.keller@intel.com \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=przemyslaw.kitszel@intel.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